engine.io-client-pure
Client for the realtime Engine
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:xmlhttprequest | AI (npm-metadata): This URL dep to a specific commit of rase-/node-XMLHttpRequest is a known, intentional pattern for engine.io-client-pure across all versions. Commit-pinned tarball provides stability. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): The new Function() call is the classic jQuery-style safe JSON fallback pattern with regex validation guards; it's in the bundled engine.io.js from the official Automattic repo and is not a malware indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals are explained by the package being a versioned fork of engine.io-client: inflated semver mirrors upstream, empty index.js is normal for browser bundles, link dump README is cosmetic. Published by a highly trusted maintainer. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.5.9 | 11 / 10 | |
| 1.5.7 | 11 / 10 | |
| 1.5.6 | 11 / 10 | |
| 1.5.4 | 11 / 10 |
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.