node-gyp-install
Manually download node/iojs header files for usage with node-gyp.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; absence is expected for this long-established package and does not indicate risk. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): request is a well-known HTTP library used legitimately here for downloading node header files; stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from ralphtheninja to mafintosh occurred in 2015; mafintosh is the canonical author listed in package.json and GitHub repo. This is a stable historical transition, not a current risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): semver is a well-established, widely-trusted package. Its addition is consistent with node-gyp-install's purpose of managing node/iojs header versions. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 9 / 1 | |
| 2.1.2 | 9 / 1 | |
| 2.1.1 | 8 / 1 | |
| 2.1.0 | 8 / 1 | |
| 2.0.1 | 8 / 1 | |
| 2.0.0 | 8 / 1 | |
| 1.4.3 | 7 / 1 | |
| 1.4.2 | 7 / 1 | |
| 1.4.1 | 6 / 1 | |
| 1.3.1 | 3 / 1 | |
| 1.2.0 | 3 / 1 | |
| 1.1.0 | 3 / 1 |
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsThis version was published by a different npm account than previous versions on 2015-09-21. 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.
v2.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-09-08. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.