@opra/socketio
Opra Socket.IO adapter
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): Monorepo sub-package versioned in lockstep with parent; inflated semver and thin README are expected patterns here. | ai | |
| phantom-deps | phantom-dep:valgen | AI (phantom-deps): Declared dep used transitively or via config; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@jsopen/objects | AI (phantom-deps): Declared dep used transitively or via config; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit runtime dep for TypeScript-compiled ESM packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:@browsery/type-is | AI (phantom-deps): Referenced in config files as documented; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:iconv-lite | AI (phantom-deps): Referenced in config files as documented; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:content-type | AI (phantom-deps): Referenced in config files as documented; not a direct import by design. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.28.5 | 7 / 0 | |
| 1.28.4 | 7 / 0 | |
| 1.28.3 | 7 / 0 | |
| 1.28.2 | 7 / 0 | |
| 1.28.1 | 7 / 0 | |
| 1.28.0 | 7 / 0 | |
| 1.27.4 | 7 / 0 | |
| 1.27.2 | 7 / 0 | |
| 1.27.1 | 7 / 0 | |
| 1.26.3 | 7 / 0 | |
| 1.26.2 | 7 / 0 | |
| 1.25.6 | 7 / 0 | |
| 1.25.5 | 7 / 0 | |
| 1.25.4 | 7 / 0 | |
| 1.25.2 | 7 / 0 | |
| 1.25.1 | 7 / 0 | |
| 1.22.1 | 7 / 0 | |
| 1.20.0 | 7 / 0 |
v1.28.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.