install-peerdeps
CLI to automatically install peerDeps
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:request | AI (dependencies): request is a well-known HTTP library used intentionally for npm registry queries; its use is appropriate and stable for this package. | ai | |
| phantom-deps | phantom-dep:request | AI (phantom-deps): Package uses Babel transpilation; static import analysis may miss usage in compiled output. request is a declared runtime dep used for npm registry HTTP calls. | ai | |
| phantom-deps | phantom-dep:https-proxy-agent | AI (phantom-deps): Proxy support is a documented feature; may be conditionally imported in transpiled code. Not a security concern. | ai | |
| phantom-deps | phantom-dep:request-promise-native | AI (phantom-deps): Companion to request for promise-based HTTP; expected usage pattern in this package's transpiled source. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): install-peerdeps is a CLI that spawns npm/yarn to install packages; child_process usage is expected and the import in question is in a test file. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.0.7 | 5 / 15 | |
| 3.0.6 | 5 / 15 | |
| 3.0.5 | 5 / 15 | |
| 3.0.4 | 5 / 15 | |
| 3.0.3 | 5 / 15 | |
| 3.0.2 | 5 / 15 | |
| 3.0.1 | 5 / 15 | |
| 3.0.0 | 8 / 15 | |
| 2.0.3 | 8 / 15 | |
| 2.0.2 | 8 / 15 | |
| 2.0.1 | 8 / 15 | |
| 2.0.0 | 8 / 15 | |
| 1.11.0 | 8 / 14 | |
| 1.10.2 | 8 / 13 | |
| 1.10.1 | 8 / 13 | |
| 1.10.0 | 8 / 13 | |
| 1.9.0 | 8 / 13 | |
| 1.8.0 | 7 / 13 | |
| 1.7.1 | 6 / 13 | |
| 1.7.0 | 7 / 13 | |
| 1.6.0 | 6 / 13 | |
| 1.5.0 | 6 / 13 | |
| 1.4.1 | 6 / 13 | |
| 1.4.0 | 6 / 13 | |
| 1.3.0 | 4 / 11 | |
| 1.2.0 | 4 / 11 | |
| 1.1.3 | 4 / 11 | |
| 1.1.2 | 4 / 7 | |
| 1.1.1 | 4 / 7 | |
| 1.1.0 | 4 / 7 | |
| 1.0.2 | 4 / 5 | |
| 1.0.1 | 4 / 5 | |
| 1.0.0 | 4 / 5 | |
| 0.0.1 | 3 / 0 |
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
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.