@trezor/blockchain-link No license 53 versions

@trezor/blockchain-link

npm Repository Homepage

53

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

prusnaktsusanka-sltrezor-cimartin_varmuzatrezor-admin

Keywords

Trezorblockchainblockbookjavascript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Trusted trezor-ci publisher; publish-env metadata change, not malicious.	ai	2026/07/22
dependencies	unvetted-dep:@everstake/wallet-sdk	AI (dependencies): Staking SDK addition consistent with package's blockchain-integration purpose; from trusted publisher.	ai	2026/07/09
source-diff	encoded-string-file:lib/workers/electrum/devrun.js	AI (source-diff): Test-fixture xpubs/tx hex in dev-run script; benign and recurring for this package.	ai	2026/07/09
publish-pattern	dormant-publish	AI (publish-pattern): Active Trezor monorepo package; publish gaps are normal for individual sub-packages.	ai	2026/05/09
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	2026/04/28
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	2026/04/28
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	2026/04/28
phantom-deps	phantom-dep:stream-browserify	AI (phantom-deps): Browser polyfill referenced in webpack config; same pattern as crypto-browserify.	ai	2026/04/28
phantom-deps	phantom-dep:@types/web	AI (phantom-deps): Type-only package loaded by convention; no runtime import needed.	ai	2026/04/28

Versions (showing 53 of 53)

Version	Deps	Published
2.6.2	18 / 9	2026-04-22
2.6.1	18 / 9	2025-12-22
2.6.0	18 / 9	2025-12-16
2.5.4	18 / 9	2025-10-23
2.5.3	17 / 10	2025-09-18
2.5.2	16 / 10	2025-07-11
2.5.1	16 / 10	2025-06-25
2.5.0	16 / 11	2025-06-03
2.4.5	14 / 11	2025-05-15
2.4.4	14 / 11	2025-04-08
2.4.3	14 / 11	2025-03-19
2.4.2	14 / 11	2025-03-14
2.4.1	14 / 11	2025-03-06
2.4.0	14 / 11	2025-02-26
2.3.6	12 / 11	2024-12-13
2.3.5	12 / 11	2024-12-09
2.3.4	12 / 11	2024-12-02
2.3.3	12 / 11	2024-11-26
2.3.2	12 / 10	2024-11-19
2.3.1	11 / 10	2024-09-24
2.3.0	11 / 10	2024-08-29
2.2.0	11 / 10	2024-07-02
2.1.30	11 / 10	2024-05-30
2.1.29	12 / 10	2024-04-30
2.1.28	12 / 10	2024-03-28
2.1.27	12 / 10	2024-03-06
2.1.26	12 / 10	2024-02-28
2.1.25	12 / 13	2024-02-12
2.1.23	12 / 13	2024-01-29
2.1.22	12 / 13	2024-01-22
2.1.21	12 / 13	2024-01-05
2.1.20	12 / 13	2023-12-18
2.1.19	12 / 13	2023-11-28
2.1.18	10 / 13	2023-10-26
2.1.17	10 / 13	2023-09-19
2.1.16	10 / 13	2023-08-28
2.1.15	10 / 13	2023-08-02
2.1.14	10 / 13	2023-07-20
2.1.13	10 / 11	2023-05-23
2.1.12	10 / 11	2023-05-16
2.1.11	10 / 10	2023-05-03
2.1.10	10 / 10	2023-04-20
2.1.9	10 / 10	2023-04-19
2.1.8	8 / 10	2023-03-01
2.1.7	8 / 11	2023-01-27
2.1.6	8 / 11	2022-12-13
2.1.5	8 / 11	2022-11-15
2.1.4	8 / 11	2022-09-12
2.1.3	8 / 7	2022-03-30
2.1.2	8 / 7	2022-03-29
2.1.1	7 / 7	2022-02-16
2.1.0	7 / 7	2022-02-14
2.0.0	4 / 7	2022-01-19

v2.4.4

1 finding

LOW No provenance attestation provenance

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

v2.4.3

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.6

1 finding

LOW No provenance attestation provenance

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

v2.3.5

1 finding

LOW No provenance attestation provenance

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

v2.3.4

1 finding

LOW No provenance attestation provenance

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

v2.3.3

1 finding

LOW No provenance attestation provenance

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

v2.3.2

2 findings

HIGH Long encoded string in modified file: lib/workers/electrum/devrun.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v2.3.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.30

1 finding

LOW No provenance attestation provenance

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

v2.1.29

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

1 finding

LOW No provenance attestation provenance

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

v2.1.27

1 finding

LOW No provenance attestation provenance

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

v2.1.26

1 finding

LOW No provenance attestation provenance

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

v2.1.25

1 finding

LOW No provenance attestation provenance

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

v2.1.23

1 finding

LOW No provenance attestation provenance

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

v2.1.22

1 finding

LOW No provenance attestation provenance

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

v2.1.21

1 finding

LOW No provenance attestation provenance

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

v2.1.20

1 finding

LOW No provenance attestation provenance

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

v2.1.19

1 finding

LOW No provenance attestation provenance

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

v2.1.18

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.17

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.16

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.15

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.14

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.13

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.12

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.11

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.10

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.9

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.8

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.7

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.6

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: trezor-ci.

LOW No provenance attestation provenance

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

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: martin_varmuza → trezor-ci (on 2022-09-12, known maintainer) provenance

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2022-09-12, but trezor-ci is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: trezor-ci → martin_varmuza (on 2022-03-29, known maintainer) provenance

This version was published by a different npm account (martin_varmuza) than the most recent previously approved version (trezor-ci) on 2022-03-29, but martin_varmuza is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.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.0.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.