← Home

@1sat/client

npm
28
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

dcasegrwildsatchmo

Keywords

1satbsvordinalsclientapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. ai

Versions (showing 28 of 28)

Version Deps Published
0.0.47 2 / 2
0.0.46 2 / 2
0.0.45 2 / 2
0.0.43 2 / 2
0.0.42 2 / 2
0.0.40 2 / 2
0.0.39 2 / 2
0.0.38 2 / 2
0.0.37 2 / 2
0.0.36 2 / 2
0.0.35 2 / 2
0.0.34 2 / 2
0.0.33 2 / 2
0.0.32 2 / 2
0.0.31 2 / 2
0.0.30 2 / 2
0.0.29 2 / 2
0.0.28 2 / 2
0.0.27 2 / 2
0.0.26 2 / 2
0.0.25 2 / 2
0.0.24 2 / 2
0.0.23 2 / 2
0.0.22 2 / 2
0.0.21 2 / 2
0.0.20 2 / 2
0.0.3 2 / 2
0.0.1 3 / 2

v0.0.47

1 finding
INFO No provenance attestation provenance

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

v0.0.46

1 finding
INFO No provenance attestation provenance

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

v0.0.45

1 finding
INFO No provenance attestation provenance

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

v0.0.43

1 finding
INFO No provenance attestation provenance

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

v0.0.42

1 finding
INFO No provenance attestation provenance

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

v0.0.40

1 finding
INFO No provenance attestation provenance

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

v0.0.39

1 finding
INFO No provenance attestation provenance

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