← Home

@trezor/transport

npm Repository
10
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

Keywords

Trezortransport

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): 127.0.0.1:21325 is the documented Trezor Bridge localhost endpoint; stable for this package. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding is standard protocol buffer framing for Trezor device communication, not malicious payload hiding. ai
dependencies unvetted-dep:@trezor/protobuf AI (dependencies): First-party sibling package from trezor/trezor-suite monorepo; stable false positive. ai
dependencies unvetted-dep:@trezor/protocol AI (dependencies): First-party sibling package from trezor/trezor-suite monorepo; stable false positive. ai
dependencies unvetted-dep:@trezor/type-utils AI (dependencies): First-party sibling package from trezor/trezor-suite monorepo; stable false positive. ai

Versions (showing 10 of 10)

Version Deps Published
1.6.3 6 / 9
1.6.2 6 / 9
1.6.1 6 / 9
1.6.0 6 / 9
1.5.4 6 / 9
1.5.3 6 / 11
1.5.2 6 / 11
1.5.1 6 / 11
1.5.0 5 / 11
1.4.5 5 / 11

v1.6.3

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

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v1.5.3

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

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