@metamask/compliance-controller
Manages OFAC compliance checks for wallet addresses
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:reselect | AI (phantom-deps): Reselect is a selector library commonly used transitively through controller dependencies in monorepo patterns. | ai | |
| phantom-deps | phantom-dep:@metamask/messenger | AI (phantom-deps): Same-org dependency; typical for MetaMask monorepo where internal packages re-export shared utilities. | ai | |
| phantom-deps | phantom-dep:@metamask/superstruct | AI (phantom-deps): Same-org dependency; used transitively through base-controller or other internal packages. | ai | |
| phantom-deps | phantom-dep:@metamask/base-controller | AI (phantom-deps): Same-org dependency; core controller base likely re-exported or used transitively. | ai | |
| phantom-deps | phantom-dep:@metamask/controller-utils | AI (phantom-deps): Same-org dependency; utilities package typical for monorepo transitive usage patterns. | ai | |
| phantom-deps | phantom-dep:@metamask/utils | AI (phantom-deps): Same-org MetaMask package; declared in dependencies, stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 6 / 11 | |
| 2.0.1 | 6 / 11 | |
| 2.0.0 | 6 / 11 | |
| 1.0.2 | 6 / 11 | |
| 1.0.1 | 6 / 11 | |
| 1.0.0 | 6 / 11 |
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.