← Home

@trezor/blockchain-link

npm Repository Homepage
9
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

prusnaktsusanka-sltrezor-cimartin_varmuzatrezor-admin

Keywords

Trezorblockchainblockbookjavascript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Active Trezor monorepo package; publish gaps are normal for individual sub-packages. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decode used to display OP_RETURN data as ASCII string — no code execution, stable pattern for this blockchain library. ai
phantom-deps phantom-dep:crypto-browserify AI (phantom-deps): Browser polyfill referenced in webpack config; not directly imported but legitimately used as a build-time alias. ai
phantom-deps phantom-dep:stream-browserify AI (phantom-deps): Browser polyfill referenced in webpack config; same pattern as crypto-browserify. ai
phantom-deps phantom-dep:@types/web AI (phantom-deps): Type-only package loaded by convention; no runtime import needed. ai
phantom-deps phantom-dep:@solana/rpc-types AI (phantom-deps): Referenced in config files as part of Solana ecosystem; stable false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
2.6.2 18 / 9
2.6.1 18 / 9
2.6.0 18 / 9
2.5.4 18 / 9
2.5.3 17 / 10
2.5.2 16 / 10
2.5.1 16 / 10
2.5.0 16 / 11
2.4.5 14 / 11

v2.6.2

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.

v2.6.1

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.

v2.6.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.

v2.5.4

1 finding
LOW No provenance attestation provenance

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

v2.5.3

1 finding
LOW No provenance attestation provenance

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

v2.5.2

1 finding
LOW No provenance attestation provenance

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

v2.5.1

1 finding
LOW No provenance attestation provenance

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

v2.5.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.

v2.4.5

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.