The Capgo CLI writes sensitive local files (.capgo API key file and build credentials JSON) using unsafe file operations that follow symlinks and do not…
Full advisory text at GitHub advisory or OSV.
npm package report
Is @capgo/cli safe?
@capgo/cli (npm) has 1 known vulnerability, the worst rated HIGH. Upgrade to 7.84.6 or later to clear it. No malicious-package signal is recorded.
// reach
19 direct dependencies
6 carry known advisories, worst CRITICAL
0 packages depend on it
an advisory here reaches each of them
Create a free accountfor every dependency path, dependent and what to upgrade
// ai model usage
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
cvss
7.5
high
severity band, no base score published
epss
not scored
chance of exploitation in 30 days
xyz score
4.1
medium
CyberXYZ composite out of 10
fig. 01 — GHSA-8mpm-q7mh-8fvh, the advisory selected below
// 1 advisories
Is @capgo/cli safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for @capgo/cli (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does @capgo/cli have known vulnerabilities?
Yes. CyberXYZ records 1 known vulnerability for @capgo/cli (npm), the worst rated HIGH. They are GHSA-8mpm-q7mh-8fvh.
Which version of @capgo/cli should I use?
7.84.6 or later clears every advisory recorded for @capgo/cli (npm). Check the release you pick before installing it.
How do I check @capgo/cli before installing?
Search @capgo/cli in CyberXYZ Check at https://cyberxyz.io/check?q=%40capgo%2Fcli. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 10:00 UTC. The most recent advisory here was published 2026-03-18. Updated continuously from NVD, GHSA, OSV and CNA feeds.