npm package report

Is @capgo/cli safe?

1 known vulnerability, worst severity HIGH.

cvss
7.5

how bad it is if exploited, out of 10

epss
not scored

chance of exploitation in the next 30 days

xyz score
4.1

CyberXYZ composite, out of 10

fig. 01 — GHSA-8mpm-q7mh-8fvh, the advisory selected below

// advisories

GHSA-8mpm-q7mh-8fvh

HIGH

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 enforce safe permissions. This allows an attacker-controlled repository to cause arbitrary file overwrite on the developer’s machine when the developer runs the CLI inside that repo. Additionally, global build credentials are written with world-re

Affected
>=0, <7.84.6, < 7.84.6
Fixed in
7.84.6
Weakness
CWE-276
Published
2026-03-18
Source
osv

OSV


// dependencies

5 direct, 3 carrying known advisories, worst CRITICAL

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.


Checked 2026-09-22 at 02:32 UTC. The most recent advisory here was published 2026-03-18. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @capgo/cli safe? npm package security report | CyberXYZ