cloudflared
1
Versions
—
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
jacoblincool
Keywords
cloudflaredtunnelmacoswindowslinuxclilib
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): Postinstall fetches the official cloudflared binary — standard binary-wrapper pattern, consistent across all versions of this package. No obfuscation or suspicious network targets. | ai | |
| provenance | no-provenance | AI (provenance): Established package (1371 days, 22 versions); lack of provenance is common and not a risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 0 / 16 |
v0.7.1
2 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: node scripts/postinstall.mjs && node lib/cloudflared.js bin install latest
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.