@metamask/network-controller
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:async-mutex | AI (phantom-deps): async-mutex is a declared runtime dependency in package.json; phantom-dep heuristic misfires here. | ai | |
| provenance | no-provenance | AI (provenance): Established MetaMask monorepo package; lack of provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 32.0.0 | 20 / 22 | |
| 31.1.0 | 20 / 22 | |
| 31.0.0 | 20 / 22 | |
| 30.1.0 | 20 / 22 | |
| 30.0.1 | 20 / 21 | |
| 30.0.0 | 20 / 21 | |
| 29.0.0 | 20 / 21 | |
| 28.0.0 | 19 / 21 | |
| 27.2.0 | 19 / 21 | |
| 27.1.0 | 20 / 21 | |
| 27.0.0 | 20 / 21 | |
| 26.0.0 | 19 / 21 |
v32.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.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.
v27.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.
v26.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.