@metamask/approval-controller MIT 2 versions

@metamask/approval-controller

npm Repository Homepage

Manages requests that require user approval

Versions

MIT

License

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

danfinlaykumavismetamaskbotgudahtt

Keywords

MetaMaskEthereum

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@metamask/messenger	AI (dependencies): First-party MetaMask monorepo sibling dependency; stable pattern across versions.	ai	2026/04/28
dependencies	unvetted-dep:@metamask/rpc-errors	AI (dependencies): First-party MetaMask monorepo sibling dependency; stable pattern across versions.	ai	2026/04/28
dependencies	unvetted-dep:@metamask/base-controller	AI (dependencies): First-party MetaMask monorepo sibling dependency; stable pattern across versions.	ai	2026/04/28

Versions (showing 2 of 2)

Version	Deps	Published
9.0.1	5 / 10	2026-03-26
9.0.0	5 / 10	2026-03-17

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.