← Home

@metamask/approval-controller

npm Repository Homepage

Manages requests that require user approval

3
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

kumavismetamaskbotgudahtt

Keywords

EthereumMetaMask

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from metamaskbot to GitHub Actions CI publishing; SLSA attestation confirms legitimate provenance. ai
maintainer-change maintainer-removed AI (maintainer-change): Normal team change in MetaMask org; no signs of takeover. ai
dependencies unvetted-dep:@metamask/messenger AI (dependencies): First-party MetaMask monorepo sibling dependency; stable pattern across versions. ai
dependencies unvetted-dep:@metamask/rpc-errors AI (dependencies): First-party MetaMask monorepo sibling dependency; stable pattern across versions. ai
dependencies unvetted-dep:@metamask/base-controller AI (dependencies): First-party MetaMask monorepo sibling dependency; stable pattern across versions. ai

Versions (showing 3 of 3)

Version Deps Published
9.0.2 5 / 10
9.0.1 5 / 10
9.0.0 5 / 10

v9.0.2

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.

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

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