@npmcli/installed-package-contents
Get the list of files installed in a package in node_modules, including bundled dependencies
Supply chain provenance
Status for the latest visible version.
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): Known npm CLI team transition from old npm Inc. maintainers to current GitHub/npm team (gar, lukekarrys, fritzy, nlf, saquibkhan). Not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are former npm CLI team members; this is a known organizational transition. | ai | |
| provenance | publisher-changed | AI (provenance): isaacs → gar is a well-known legitimate transition within the npm CLI team at GitHub. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (fritzy, nlf, gar, lukekarrys) are the current npm CLI team at GitHub. | ai | |
| phantom-deps | phantom-dep:readdir-scoped-modules | AI (phantom-deps): Scoped module inspection utility; used indirectly in package analysis. Stable for this package type. | ai | |
| phantom-deps | phantom-dep:tap-parser | AI (phantom-deps): Test infrastructure dependency; referenced in config but not direct import. Stable for npm CLI utilities. | ai | |
| phantom-deps | phantom-dep:read-package-json-fast | AI (phantom-deps): Core utility for package inspection; likely used indirectly. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Utility package for npm; react likely used in test fixtures or config. Phantom-dep false positive for this package type. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): TypeScript types for react; used alongside react dependency. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:npm-normalize-package-bin | AI (dependencies): npm-normalize-package-bin is an official npm CLI ecosystem package maintained by GitHub Inc., a well-known and trusted dependency for this package's purpose. | ai | |
| dependencies | unvetted-dep:npm-bundled | AI (dependencies): npm-bundled is an official npm CLI ecosystem package maintained by GitHub Inc., a well-known and trusted dependency for this package's purpose. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 2 / 3 | |
| 4.0.0 | 2 / 3 | |
| 3.0.0 | 2 / 3 | |
| 2.1.0 | 2 / 3 | |
| 2.0.2 | 2 / 4 | |
| 2.0.1 | 2 / 5 | |
| 2.0.0 | 2 / 5 | |
| 1.0.7 | 2 / 2 | |
| 1.0.6 | 4 / 1 | |
| 1.0.5 | 4 / 1 | |
| 1.0.4 | 4 / 1 | |
| 1.0.3 | 3 / 1 | |
| 1.0.2 | 3 / 1 | |
| 1.0.1 | 6 / 1 | |
| 1.0.0 | 6 / 1 |
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
4 findingsAll previous maintainers (adam_baldwin, ahmadnassri, annekimsey, billatnpm, claudiahdz, darcyclarke, isaacs, mikemimik, ruyadorno) were replaced by new maintainers (saquibkhan, fritzy, nlf, gar, lukekarrys). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
This version was published by a different npm account than previous versions on 2023-02-27. 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.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-10-19. 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.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-10-14. 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.0.7
2 findingsThis version was published by a different npm account than previous versions on 2021-02-08. 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.0.6
2 findingsThis version was published by a different npm account than previous versions on 2021-02-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.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
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.