@blocklet/puppeteer
1
Versions
—
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
wangshijungxw
Keywords
puppeteerchromeheadlessautomation
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Puppeteer's standard browser-download postinstall; stable pattern for this package. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Reads process.env keys only to detect npm_package_config_puppeteer_* config vars; benign config-detection pattern. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 22.11.3 | 3 / 1 |
v22.11.3
2 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: node install.mjs
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.