← Home

@metamask/eth-trezor-keyring

npm Repository Homepage

A MetaMask compatible keyring, for trezor hardware wallets

8
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

kumavisfrederikboldingmetamaskbotgudahttmrtenmcmirenaugtur

Keywords

ethereumkeyringmetamasktrezor

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@trezor/connect-plugin-ethereum AI (dependencies): Official Trezor Ethereum plugin; expected dependency for this hardware wallet keyring across all versions. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a declared runtime dependency used implicitly by TypeScript-compiled output; stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
10.1.2 12 / 23
10.1.1 12 / 23
10.1.0 12 / 23
10.0.2 12 / 23
10.0.1 12 / 23
10.0.0 12 / 23
9.1.1 12 / 23
9.1.0 11 / 23

v10.1.2

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: metamaskbot → GitHub Actions (on 2026-07-22, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (metamaskbot) on 2026-07-22, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v10.1.1

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: metamaskbot → GitHub Actions (on 2026-07-07, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (metamaskbot) on 2026-07-07, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.