@ooneex/socket
WebSocket server implementation with room management, event broadcasting, client tracking, and middleware integration for real-time applications
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
Keywords
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): @ooneex/* is a monorepo ecosystem; sparse metadata is consistent across all its packages, not a spam indicator. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 0 / 3 | |
| 1.2.15 | 0 / 3 | |
| 1.2.14 | 0 / 3 | |
| 1.2.13 | 0 / 3 | |
| 1.2.12 | 0 / 3 | |
| 1.2.11 | 0 / 3 | |
| 1.2.10 | 0 / 3 | |
| 1.2.9 | 0 / 3 | |
| 1.2.8 | 0 / 3 | |
| 1.2.6 | 0 / 3 | |
| 1.2.5 | 0 / 3 | |
| 1.2.4 | 0 / 3 | |
| 1.2.3 | 0 / 3 | |
| 1.2.2 | 0 / 3 | |
| 1.2.1 | 0 / 3 | |
| 1.2.0 | 0 / 3 | |
| 1.1.1 | 0 / 3 | |
| 1.1.0 | 0 / 3 | |
| 1.0.0 | 0 / 3 | |
| 0.17.0 | 0 / 5 | |
| 0.16.0 | 0 / 5 | |
| 0.15.0 | 0 / 5 | |
| 0.14.0 | 0 / 5 | |
| 0.13.0 | 0 / 5 | |
| 0.12.0 | 0 / 4 | |
| 0.11.0 | 0 / 4 | |
| 0.10.0 | 0 / 4 | |
| 0.9.0 | 0 / 4 | |
| 0.8.0 | 0 / 4 | |
| 0.7.0 | 0 / 4 | |
| 0.6.0 | 0 / 4 | |
| 0.5.0 | 0 / 4 | |
| 0.4.0 | 0 / 4 | |
| 0.3.0 | 0 / 4 | |
| 0.0.1 | 1 / 15 |
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.