browserify-sign (npm) has 1 known vulnerability, the worst rated HIGH. Upgrade to 4.2.2 or later to clear it. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
8 packages depend on it
an advisory here reaches each of them
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, 47th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-x9w5-v3q2-3rhw, the advisory selected below
An upper bound check issue in dsaVerify function allows an attacker to construct signatures that can be successfully verified by any public key, thus leading…
Full advisory text at GitHub advisory or NVD.
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 browserify-sign (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 browserify-sign (npm), the worst rated HIGH. They are GHSA-x9w5-v3q2-3rhw.
4.2.2 or later clears every advisory recorded for browserify-sign (npm). Check the release you pick before installing it.
Search browserify-sign in CyberXYZ Check at https://cyberxyz.io/check?q=browserify-sign. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-15 at 11:09 UTC. The most recent advisory here was published 2023-10-26. Updated continuously from NVD, GHSA, OSV and CNA feeds.