engine.io-pure
The realtime engine behind Socket.IO. Provides the foundation of a bidirectional connection between client and server
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Package is a legitimate long-standing fork of engine.io; inflated semver mirrors upstream version, README links are ecosystem docs, and the package has 10+ years of history with real downloads. | ai | |
| provenance | no-provenance | AI (provenance): Package was first published ~10 years ago, well before npm provenance attestation existed. Absence is expected and not a risk signal for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.5.9 | 4 / 5 | |
| 1.5.8 | 4 / 5 | |
| 1.5.7 | 4 / 5 | |
| 1.5.5 | 4 / 5 | |
| 1.5.4 | 4 / 5 |
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
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.5
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.