@metamask/selected-network-controller
Provides an interface to the currently selected networkClientId for a given domain
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): MetaMask core monorepo consistently publishes without Sigstore provenance; stable pattern across all versions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 26.1.1 | 7 / 14 | |
| 26.1.0 | 7 / 14 | |
| 26.0.3 | 7 / 13 | |
| 26.0.2 | 7 / 13 | |
| 26.0.1 | 7 / 13 | |
| 26.0.0 | 5 / 15 |
v26.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.