engine.io
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.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is an intentional, documented feature allowing pluggable WebSocket engines (e.g., uws). Not a security risk for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): engine.io is a well-established, legitimate package; bogus-package signals are false positives for this mature socketio project. | ai | |
| phantom-deps | phantom-dep:@types/cookie | AI (phantom-deps): @types/cookie is a TypeScript type declaration used at compile time; phantom-dep firing on @types/* packages is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): TypeScript type definitions are legitimately declared for a Node.js networking library; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/cors | AI (phantom-deps): TypeScript type definitions are legitimately declared for CORS support; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): TypeScript type definitions are legitimately declared for Node.js; loaded by convention. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 6.6.8 | 10 / 0 | |
| 6.6.7 | 10 / 0 | |
| 6.6.6 | 10 / 0 | |
| 6.6.5 | 9 / 0 | |
| 6.6.4 | 9 / 0 | |
| 6.6.3 | 9 / 0 | |
| 6.6.2 | 10 / 0 | |
| 6.6.1 | 10 / 0 | |
| 6.6.0 | 10 / 15 | |
| 6.5.5 | 10 / 15 | |
| 6.5.4 | 10 / 15 | |
| 6.5.3 | 10 / 15 | |
| 6.5.2 | 10 / 15 | |
| 6.5.1 | 10 / 15 | |
| 6.5.0 | 10 / 15 | |
| 6.4.2 | 10 / 13 | |
| 3.6.2 | 6 / 14 | |
| 3.6.1 | 6 / 14 |
v6.6.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.