@trezor/blockchain-link-utils

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Manual publish by known maintainer in trezor monorepo; metadata gap, not malicious.	ai	2026/07/22
dependencies	unvetted-dep:@everstake/wallet-sdk	AI (dependencies): Legitimate staking SDK dep fitting package's blockchain-link purpose.	ai	2026/07/09
maintainer-change	maintainer-added	AI (maintainer-change): trezor-admin addition is consistent with org-level CI account management for the Trezor monorepo.	ai	2026/05/09
publish-pattern	new-deps-added	AI (publish-pattern): @trezor/protobuf is a first-party Trezor package at matching version; low risk.	ai	2026/05/09
publish-pattern	dormant-publish	AI (publish-pattern): Trezor monorepo; versioned releases across many packages; dormancy reflects release cadence, not takeover.	ai	2026/05/09
bogus-package	bogus-package	AI (bogus-package): Trezor monorepo sub-package; sparse metadata is expected for internal utility packages.	ai	2026/04/28
npm-metadata	no-description	AI (npm-metadata): Consistent with Trezor monorepo sub-package pattern across all versions.	ai	2026/04/28

Versions (showing 40 of 40)

Version	Deps	Published
1.5.2	6 / 8	2026-02-26
1.5.1	6 / 8	2025-12-22
1.5.0	6 / 8	2025-12-16
1.4.4	6 / 8	2025-10-23
1.4.3	5 / 8	2025-09-18
1.4.2	5 / 8	2025-07-11
1.4.1	5 / 8	2025-06-25
1.4.0	5 / 8	2025-06-03
1.3.5	4 / 8	2025-05-15
1.3.4	4 / 8	2025-04-08
1.3.3	3 / 4	2025-03-19
1.3.2	3 / 4	2025-03-14
1.3.1	3 / 4	2025-03-06
1.3.0	4 / 4	2025-02-26
1.2.6	3 / 4	2024-12-13
1.2.5	3 / 4	2024-12-09
1.2.4	4 / 4	2024-12-02
1.2.3	4 / 4	2024-11-26
1.2.2	4 / 3	2024-11-19
1.2.1	4 / 3	2024-09-24
1.2.0	4 / 3	2024-08-29
1.1.0	4 / 3	2024-07-02
1.0.18	4 / 3	2024-05-30
1.0.16	4 / 3	2024-03-28
1.0.15	4 / 3	2024-02-28
1.0.14	4 / 6	2024-02-09
1.0.13	4 / 6	2024-01-29
1.0.12	4 / 6	2024-01-22
1.0.11	4 / 6	2024-01-05
1.0.10	4 / 6	2023-12-18
1.0.9	4 / 6	2023-11-28
1.0.8	2 / 6	2023-10-26
1.0.7	2 / 6	2023-09-19
1.0.6	2 / 6	2023-08-28
1.0.5	2 / 6	2023-08-02
1.0.4	2 / 6	2023-07-20
1.0.3	2 / 6	2023-05-16
1.0.2	2 / 6	2023-05-03
1.0.1	2 / 6	2023-04-20
1.0.0	2 / 6	2023-04-19

v1.3.4

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.6

1 finding

LOW No provenance attestation provenance

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

v1.2.5

1 finding

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.18

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.

v1.0.16

1 finding

LOW No provenance attestation provenance

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

v1.0.15

1 finding

LOW No provenance attestation provenance

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

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

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 2023-12-18, known maintainer) provenance

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-12-18, 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.

v1.0.9

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 2023-11-28, known maintainer) provenance

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-11-28, 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.

v1.0.8

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

INFO Publisher changed: martin_varmuza → trezor-ci (on 2023-10-26, known maintainer) provenance

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-10-26, 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.

v1.0.7

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

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

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-09-19, 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.

v1.0.6

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

INFO Publisher changed: martin_varmuza → trezor-ci (on 2023-08-28, known maintainer) provenance

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-08-28, 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.

v1.0.5

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

INFO Publisher changed: martin_varmuza → trezor-ci (on 2023-08-02, known maintainer) provenance

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-08-02, 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.

v1.0.4

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

INFO Publisher changed: martin_varmuza → trezor-ci (on 2023-07-20, known maintainer) provenance

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-07-20, 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.

v1.0.3

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

INFO Publisher changed: martin_varmuza → trezor-ci (on 2023-05-16, known maintainer) provenance

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-05-16, 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.

v1.0.2

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

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

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-05-03, 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.

v1.0.1

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

INFO Publisher changed: martin_varmuza → trezor-ci (on 2023-04-20, known maintainer) provenance

This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-04-20, 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.

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