@randajan/koa-io-session
Simple bridge between koa-session and socket.io. Shares a unified session across HTTP and WebSocket using a common session store.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; publisher does not use Sigstore attestation. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 3 / 4 | |
| 3.1.0 | 3 / 4 | |
| 3.0.1 | 3 / 4 | |
| 3.0.0 | 3 / 4 | |
| 2.2.0 | 3 / 4 | |
| 2.1.0 | 3 / 4 | |
| 1.0.0 | 4 / 4 |
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.