natives
Do stuff with Node.js's native JavaScript modules
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): isaacs → addaleax transition in 2018 is a well-known legitimate handoff; addaleax is a prominent Node.js core contributor with a strong npm track record (172 approved, 0 rejected). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): addaleax is a trusted publisher; this addition is part of the documented 2018 legitimate maintainer transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): isaacs removal is part of the same legitimate 2018 handoff; no evidence of compromise. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from isaacs to addaleax in 2018 is a known legitimate transfer; addaleax has strong ecosystem trust. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require of native module IDs is the core functionality of this package; not a security concern in this context. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.1.6 | 0 / 1 | |
| 1.1.5 | 0 / 1 | |
| 1.1.4 | 0 / 1 | |
| 1.1.3 | 0 / 1 | |
| 1.1.2 | 0 / 1 | |
| 1.1.1 | 0 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.2 | 0 / 1 | |
| 1.0.1 | 0 / 1 | |
| 1.0.0 | 0 / 1 |
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
3 findingsAll previous maintainers (isaacs) were replaced by new maintainers (addaleax). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2018-04-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
3 findingsAll previous maintainers (isaacs) were replaced by new maintainers (addaleax). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2018-03-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.