@trezor/blockchain-link-types
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Known-maintainer manual publish in official @trezor scope; benign publish-env change. | ai | |
| dependencies | unvetted-dep:@everstake/wallet-sdk | AI (dependencies): Legitimate staking SDK dep added by trusted Trezor monorepo publisher. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @trezor/utils is a first-party Trezor package; not a suspicious third-party dependency injection. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): trezor-admin is within the same Trezor org; consistent with internal CI restructuring. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Trezor monorepo sub-package; missing metadata is expected for scoped types packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo types sub-package; missing description is consistent across all Trezor scoped packages. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.5.1 | 2 / 2 | |
| 1.5.0 | 2 / 2 | |
| 1.4.4 | 2 / 2 | |
| 1.4.3 | 2 / 2 | |
| 1.4.2 | 1 / 2 | |
| 1.4.1 | 1 / 2 | |
| 1.4.0 | 1 / 2 | |
| 1.3.5 | 1 / 2 | |
| 1.3.4 | 2 / 1 | |
| 1.3.3 | 3 / 1 | |
| 1.3.2 | 3 / 1 | |
| 1.3.1 | 3 / 1 | |
| 1.3.0 | 4 / 1 | |
| 1.2.5 | 3 / 1 | |
| 1.2.4 | 3 / 1 | |
| 1.2.3 | 3 / 1 | |
| 1.2.2 | 3 / 1 | |
| 1.2.1 | 4 / 1 | |
| 1.2.0 | 4 / 1 | |
| 1.1.0 | 4 / 1 | |
| 1.0.17 | 4 / 2 | |
| 1.0.15 | 4 / 2 | |
| 1.0.14 | 4 / 2 | |
| 1.0.13 | 4 / 4 | |
| 1.0.11 | 0 / 8 | |
| 1.0.10 | 0 / 7 | |
| 1.0.9 | 0 / 7 | |
| 1.0.8 | 0 / 7 | |
| 1.0.7 | 0 / 6 | |
| 1.0.6 | 0 / 6 | |
| 1.0.5 | 0 / 6 | |
| 1.0.4 | 0 / 6 | |
| 1.0.3 | 0 / 6 | |
| 1.0.2 | 0 / 6 | |
| 1.0.1 | 0 / 6 | |
| 1.0.0 | 0 / 5 |
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.7
3 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.6
3 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.5
3 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4
3 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
3 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
3 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.