@metamask/profile-metrics-controller
Sample package to illustrate best practices for controllers
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): MetaMask migrated from metamaskbot to GitHub Actions CI publishing; consistent across their monorepo. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @metamask/superstruct is an internal MetaMask dependency; benign addition. | ai | |
| provenance | no-provenance | AI (provenance): MetaMask core packages consistently publish without Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 11 / 12 | |
| 3.1.6 | 10 / 12 | |
| 3.1.5 | 10 / 12 | |
| 3.1.4 | 10 / 12 | |
| 3.1.3 | 10 / 12 | |
| 3.1.2 | 10 / 12 | |
| 3.1.1 | 10 / 12 | |
| 3.1.0 | 10 / 12 | |
| 3.0.4 | 10 / 12 | |
| 3.0.3 | 10 / 12 | |
| 3.0.2 | 10 / 12 | |
| 3.0.1 | 10 / 12 | |
| 3.0.0 | 10 / 12 | |
| 2.0.0 | 9 / 12 | |
| 1.1.0 | 9 / 12 | |
| 1.0.0 | 9 / 12 |
v3.2.0
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.