@trezor/blockchain-link-utils
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Trezor monorepo; versioned releases across many packages; dormancy reflects release cadence, not takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @trezor/protobuf is a first-party Trezor package at matching version; low risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): trezor-admin addition is consistent with org-level CI account management for the Trezor monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Trezor monorepo sub-package; sparse metadata is expected for internal utility packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with Trezor monorepo sub-package pattern across all versions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.5.2 | 6 / 8 | |
| 1.5.1 | 6 / 8 | |
| 1.5.0 | 6 / 8 | |
| 1.4.4 | 6 / 8 | |
| 1.4.3 | 5 / 8 | |
| 1.4.2 | 5 / 8 | |
| 1.4.1 | 5 / 8 | |
| 1.4.0 | 5 / 8 | |
| 1.3.5 | 4 / 8 |
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.