@nmtjs/ws-transport
WebSocket server transport for Neemata runtimes.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:uWebSockets.js | AI (dependencies): uWebSockets.js is intentionally distributed via GitHub; pinned to a specific tag (v20.51.0), not a floating ref. | ai | |
| npm-metadata | url-dep:uWebSockets.js | AI (npm-metadata): Same rationale: uWebSockets.js is a known library distributed only via GitHub, pinned to a specific version tag. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.15.3 | 1 / 5 | |
| 0.15.2 | 1 / 5 | |
| 0.15.1 | 1 / 5 | |
| 0.15.0 | 1 / 5 | |
| 0.14.5 | 1 / 4 | |
| 0.14.4 | 1 / 4 | |
| 0.14.3 | 1 / 4 | |
| 0.14.2 | 1 / 4 | |
| 0.14.1 | 1 / 4 | |
| 0.14.0 | 1 / 4 | |
| 0.13.1 | 1 / 4 | |
| 0.13.0 | 1 / 4 | |
| 0.12.4 | 1 / 4 | |
| 0.11.5 | 1 / 4 | |
| 0.10.4 | 1 / 4 | |
| 0.8.0 | 1 / 4 | |
| 0.7.6 | 4 / 1 | |
| 0.7.5 | 4 / 1 | |
| 0.7.4 | 4 / 1 |
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
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.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.