← Home

@dxos/websocket-rpc

npm Repository Homepage

websocket-rpc

11
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

richburdonmarik_dwittjosiahdxos-botmykola-vrmchk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from dxos-bot to GitHub Actions CI is a documented pipeline migration for the dxos monorepo; SLSA attestation confirms integrity. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of individual maintainer consistent with org-level CI takeover of publishing; no malicious indicators present. ai
phantom-deps phantom-dep:ws AI (phantom-deps): ws is a declared runtime dep used by isomorphic-ws; phantom-dep heuristic fires incorrectly here. ai
phantom-deps phantom-dep:@dxos/protocols AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic is a false positive for this package. ai

Versions (showing 11 of 11)

Version Deps Published
0.10.0 7 / 0
0.9.0 7 / 0
0.8.3 7 / 0
0.8.2 7 / 0
0.8.1 7 / 0
0.8.0 7 / 0
0.7.4 7 / 0
0.7.3 7 / 0
0.7.2 7 / 0
0.7.1 7 / 0
0.7.0 7 / 0

v0.10.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.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.