← Home

@bsv/authsocket-client

npm Repository Homepage

Mutually Authenticated Web Sockets Client

4
Versions
SEE LICENSE IN LICENSE.txt
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

johngalt5loftsteinndkellenbraydudetyeverett

Keywords

BSVBlockchainAuthenticationWebsocketsSockets

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Package has SLSA provenance attestation which supersedes gitHead as a supply-chain integrity signal. ai
publish-pattern dormant-publish AI (publish-pattern): Published via GitHub Actions with SLSA attestation from a known org; dormancy consistent with monorepo release cadence. ai

Versions (showing 4 of 4)

Version Deps Published
2.0.3 2 / 11
2.0.2 2 / 11
2.0.1 2 / 11
1.0.13 2 / 11

v2.0.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

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.

v2.0.2

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.

v2.0.1

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.

v1.0.13

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.