@metamask/config-registry-controller
Manages configuration registry for MetaMask
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 dependency; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@metamask/controller-utils | AI (dependencies): First-party MetaMask monorepo dependency; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@metamask/keyring-controller | AI (dependencies): First-party MetaMask monorepo dependency; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@metamask/polling-controller | AI (dependencies): First-party MetaMask monorepo dependency; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@metamask/profile-sync-controller | AI (dependencies): First-party MetaMask monorepo dependency; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@metamask/remote-feature-flag-controller | AI (dependencies): First-party MetaMask monorepo dependency; consistent with package purpose. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 10 / 12 | |
| 0.3.2 | 10 / 12 | |
| 0.3.1 | 10 / 12 | |
| 0.3.0 | 10 / 12 | |
| 0.2.0 | 10 / 12 | |
| 0.1.1 | 10 / 11 | |
| 0.1.0 | 10 / 11 |
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.