← Home

@metamask/money-account-upgrade-controller

npm Repository Homepage

MetaMask Money account upgrade controller

12
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

kumavismetamaskbotgudahttmrtenmcmirenaugtur

Keywords

EthereumMetaMask

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): MetaMask packages publish via GitHub Actions CI with SLSA attestation; publisher=GitHub Actions is the expected pattern. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are MetaMask org members; stable for this package. ai
provenance no-provenance AI (provenance): MetaMask/core monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. ai

Versions (showing 12 of 12)

Version Deps Published
2.0.5 10 / 11
2.0.4 10 / 11
2.0.3 10 / 11
2.0.2 10 / 11
2.0.1 10 / 11
2.0.0 10 / 11
1.3.2 6 / 10
1.3.1 6 / 10
1.3.0 6 / 10
1.2.0 6 / 10
1.1.0 6 / 10
1.0.0 4 / 11

v2.0.5

2 findings
HIGH Publisher changed: metamaskbot → GitHub Actions (on 2026-06-11) provenance

This version was published by a different npm account than previous versions on 2026-06-11. This could indicate a legitimate maintainer transition or an account compromise.

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.

v2.0.4

2 findings
HIGH Publisher changed: metamaskbot → GitHub Actions (on 2026-06-09) provenance

This version was published by a different npm account than previous versions on 2026-06-09. This could indicate a legitimate maintainer transition or an account compromise.

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.

v2.0.3

1 finding
INFO No provenance attestation provenance

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

v2.0.2

1 finding
INFO No provenance attestation provenance

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

v2.0.1

1 finding
INFO No provenance attestation provenance

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

v2.0.0

1 finding
INFO No provenance attestation provenance

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

v1.3.2

1 finding
INFO No provenance attestation provenance

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

v1.3.1

1 finding
INFO No provenance attestation provenance

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

v1.1.0

1 finding
INFO No provenance attestation provenance

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

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.