bignum releases from v0.12.2 to v0.13.0 (inclusive) used node-pre-gyp to optionally download pre-built binary versions of the addon.
Full advisory text at GitHub advisory.
npm package report
Is bignum safe?
bignum (npm) has 2 known vulnerabilities, the worst rated CRITICAL. No single fixed version is recorded that clears every advisory, so check each one below. No malicious-package signal is recorded.
// reach
0 direct dependencies
none carry a known advisory
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
9.0
critical
severity band, no base score published
epss
not scored
chance of exploitation in 30 days
xyz score
4.5
medium
CyberXYZ composite out of 10
fig. 01 — GHSA-7cgc-fjv4-52x6, the advisory selected below
// 2 advisories
Is bignum safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for bignum (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does bignum have known vulnerabilities?
Yes. CyberXYZ records 2 known vulnerabilities for bignum (npm), the worst rated CRITICAL. They are GHSA-7cgc-fjv4-52x6, GHSA-6429-3g3w-6mw5.
How do I check bignum before installing?
Search bignum in CyberXYZ Check at https://cyberxyz.io/check?q=bignum. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 05:20 UTC. The most recent advisory here was published 2023-05-24. Updated continuously from NVD, GHSA, OSV and CNA feeds.