pusher-js
1
Versions
—
License
No
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
jeremy.goldsteinmarcelcorsopushercom
Keywords
pusherclientwebsockethttpfallbackisomorphiceventspubsub
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is in integration_tests_server/index.js, a test helper only. No malicious payload hiding; stable false positive for this package. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is in the well-known json2.js polyfill (Crockford's JSON2), a legacy JSON parsing fallback. This pattern is stable and benign for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 4007-day history; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 8.5.0 | 1 / 32 |
v8.5.0
1 finding
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.