jayson
JSON-RPC 1.0/2.0 compliant server and client
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
tedeh
Keywords
jsonrpcjson-rpcrpcjsonjsonrpc-2.0jsonrpc-1.0middlewareconnectexpressforkdistributedrelayhttptcphttpstlsapi
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dependency for WebSocket transport; phantom-dep rule is a false positive for framework/transport dependencies. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): @types/ws is a declared TypeScript type definition; phantom-dep rule is expected for type packages loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a declared TypeScript type definition; phantom-dep rule is expected for type packages loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/connect | AI (phantom-deps): @types/connect is a declared TypeScript type definition; phantom-dep rule is expected for type packages loaded by convention. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 12 / 17 |
v4.3.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.