chrome-launcher
Launch latest Chrome with the Devtools Protocol port open
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 | publisher-changed | AI (provenance): paulirish is a known Chrome DevTools maintainer; legitimate transition from hoten. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy normal for stable utility; publisher is trusted GoogleChrome team member. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is intentionally listed as a runtime dep in chrome-launcher for type resolution; this is a known pattern for this package and not a security concern. | ai | |
| dependencies | unvetted-dep:lighthouse-logger | AI (dependencies): lighthouse-logger is a legitimate companion package in the Google Chrome/Lighthouse ecosystem; its use here is expected and appropriate. | ai |
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-06. 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.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.