@trezor/transport No license 38 versions

@trezor/transport

npm Repository

38

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

prusnaktsusanka-sltrezor-cimartin_varmuzatrezor-admin

Keywords

Trezortransport

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:json-stable-stringify	AI (phantom-deps): Legit dep in official Trezor transport; used at runtime, TS build hides import text.	ai	2026/07/22
phantom-deps	phantom-dep:long	AI (phantom-deps): Likely used indirectly via protobufjs; no malicious indication.	ai	2026/07/22
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	2026/05/09
semgrep	semgrep:hex-decode	AI (semgrep): Hex decoding is standard protocol buffer framing for Trezor device communication, not malicious payload hiding.	ai	2026/04/28
dependencies	unvetted-dep:@trezor/type-utils	AI (dependencies): First-party sibling package from trezor/trezor-suite monorepo; stable false positive.	ai	2026/04/28
dependencies	unvetted-dep:@trezor/protobuf	AI (dependencies): First-party sibling package from trezor/trezor-suite monorepo; stable false positive.	ai	2026/04/28
dependencies	unvetted-dep:@trezor/protocol	AI (dependencies): First-party sibling package from trezor/trezor-suite monorepo; stable false positive.	ai	2026/04/28

Versions (showing 38 of 38)

Version	Deps	Published
1.6.3	6 / 9	2026-04-22
1.6.2	6 / 9	2026-02-26
1.6.1	6 / 9	2025-12-22
1.6.0	6 / 9	2025-12-16
1.5.4	6 / 9	2025-10-23
1.5.3	6 / 11	2025-09-18
1.5.2	6 / 11	2025-07-11
1.5.1	6 / 11	2025-06-25
1.5.0	5 / 11	2025-06-03
1.4.5	5 / 11	2025-05-15
1.4.4	5 / 11	2025-04-08
1.4.3	5 / 11	2025-03-19
1.4.2	5 / 11	2025-03-14
1.4.1	5 / 11	2025-03-06
1.4.0	7 / 11	2025-02-26
1.3.7	7 / 11	2024-12-13
1.3.6	7 / 11	2024-12-09
1.3.5	7 / 11	2024-12-02
1.3.4	7 / 11	2024-11-26
1.3.3	7 / 10	2024-11-19
1.3.2	7 / 10	2024-10-01
1.3.1	7 / 10	2024-09-24
1.3.0	7 / 10	2024-08-29
1.2.0	8 / 9	2024-07-02
1.1.29	8 / 9	2024-05-30
1.1.28	8 / 9	2024-04-30
1.1.22	8 / 9	2024-01-29
1.1.19	8 / 9	2023-12-18
1.1.18	9 / 10	2023-11-28
1.1.13	8 / 10	2023-07-20
1.1.5	6 / 7	2022-11-15
1.1.4	5 / 2	2022-07-26
1.1.3	5 / 2	2022-06-17
1.1.2	5 / 2	2022-03-24
1.1.1	5 / 2	2022-03-23
1.1.0	5 / 3	2022-02-14
1.0.1	4 / 3	2021-12-13
1.0.0	4 / 3	2021-12-12

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.7

1 finding

LOW No provenance attestation provenance

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

v1.3.6

1 finding

LOW No provenance attestation provenance

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

v1.3.5

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v1.1.28

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

1 finding

LOW No provenance attestation provenance

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

v1.1.19

1 finding

LOW No provenance attestation provenance

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

v1.1.18

1 finding

LOW No provenance attestation provenance

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

v1.1.13

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

v1.1.5

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 2022-11-15, known maintainer) provenance

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

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 2022-07-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 2022-07-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.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

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

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 2022-02-14, known maintainer) provenance

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