npm-install-package
Install an npm package
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): npm-install-package's core purpose is invoking npm CLI via child_process; this import is fundamental to the package's documented functionality and not a security risk. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 0 / 16 | |
| 2.0.0 | 1 / 16 | |
| 1.1.0 | 1 / 16 | |
| 1.0.2 | 1 / 16 | |
| 1.0.1 | 2 / 16 | |
| 1.0.0 | 2 / 16 |
v2.1.0
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.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.