← Home

@trezor/blockchain-link-types

npm
8
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 8 of 8)

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

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

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

v1.4.4

1 finding
LOW No provenance attestation provenance

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

v1.4.3

1 finding
LOW No provenance attestation provenance

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

v1.4.2

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

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

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