@metamask/polling-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:@types/uuid | AI (phantom-deps): @types/uuid is a type-only dep legitimately declared as a runtime dep in this package's pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@metamask/controller-utils | AI (phantom-deps): Same-org utility package; likely used transitively or via re-exports; stable false positive for MetaMask packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 16.0.6 | 7 / 10 | |
| 16.0.5 | 7 / 10 | |
| 16.0.4 | 7 / 9 | |
| 16.0.3 | 7 / 9 | |
| 16.0.2 | 7 / 10 | |
| 16.0.1 | 7 / 10 | |
| 16.0.0 | 6 / 11 |
v16.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.