sigstore (npm) has 1 known vulnerability, the worst rated HIGH. Upgrade to 4.1.1 or later to clear it. No malicious-package signal is recorded.
6 direct dependencies
2 carry known advisories, worst MEDIUM
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 7th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-52v5-jr5w-gjxr, the advisory selected below
The documented certificateOIDs option in sigstore.verify() is accepted by the public API but discarded before verification, so required certificate extension…
Full advisory text at GitHub advisory, NVD or OSV.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for sigstore (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 1 known vulnerability for sigstore (npm), the worst rated HIGH. They are GHSA-52v5-jr5w-gjxr.
4.1.1 or later clears every advisory recorded for sigstore (npm). Check the release you pick before installing it.
Search sigstore in CyberXYZ Check at https://cyberxyz.io/check?q=sigstore. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 11:07 UTC. The most recent advisory here was published 2026-07-01. Updated continuously from NVD, GHSA, OSV and CNA feeds.