← Home

@utxorpc/sdk

npm Repository Homepage
15
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

avatxusscarmuegarawriclark

Keywords

utxorpcblockchain

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed-stale AI (provenance): 650-day stale publisher change inconsistent with account takeover. ai
source-diff source-size-tripled AI (source-diff): Explained by added browser build target (bundled mjs + sourcemap). ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): Types package used by convention, not directly imported. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding is used for blockchain hash parsing (Buffer.from(hash, 'hex')); standard pattern for this package. ai

Versions (showing 15 of 15)

Version Deps Published
0.8.2 5 / 5
0.8.1 5 / 5
0.8.0 5 / 5
0.7.0 5 / 5
0.6.8 5 / 5
0.6.7 5 / 4
0.6.6 5 / 4
0.6.5 5 / 4
0.6.4 6 / 3
0.6.3 6 / 3
0.6.2 6 / 3
0.5.0 4 / 3
0.4.0 4 / 2
0.3.0 4 / 2
0.2.0 4 / 2

v0.6.7

1 finding
LOW No provenance attestation provenance

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

v0.6.6

1 finding
LOW No provenance attestation provenance

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

v0.6.5

1 finding
LOW No provenance attestation provenance

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

v0.6.4

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.

v0.6.3

2 findings
MEDIUM Publisher changed: scarmuega → rawriclark (on 2024-10-05, unremoved on npm for 650d) provenance

This version was published by a different npm account (rawriclark) than the most recent previously approved version (scarmuega) on 2024-10-05. It has since remained available on npm for 650 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.6.2

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

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