← Home

@metamask/seedless-onboarding-controller

npm Repository Homepage

Backup and rehydrate SRP(s) using social login and password

11
Versions
MIT
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

EthereumMetaMask

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@noble/hashes AI (phantom-deps): @noble/hashes is explicitly declared as a direct dependency in package.json; phantom-dep is a false positive here. ai

Versions (showing 11 of 11)

Version Deps Published
10.1.0 11 / 16
10.0.3 11 / 16
10.0.0 11 / 16
9.1.0 11 / 16
9.0.0 11 / 15
8.1.0 11 / 15
8.0.0 11 / 15
7.1.0 11 / 15
7.0.0 10 / 16
6.1.0 9 / 17
6.0.0 9 / 16

v10.1.0

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

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-06-25, 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-06-25, 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.