@metamask/perps-controller
Controller for perpetual trading functionality in MetaMask
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@nktkas/hyperliquid | AI (dependencies): Legitimate Hyperliquid API client used intentionally in MetaMask perps trading controller; stable dependency across versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): MetaMask org regularly rotates maintainers; metamaskbot publisher has strong track record with no rejections. | ai | |
| provenance | no-provenance | AI (provenance): MetaMask monorepo package published via metamaskbot; provenance absence is consistent across their ecosystem. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 6.3.0 | 9 / 19 | |
| 6.2.0 | 9 / 19 | |
| 6.1.0 | 9 / 19 | |
| 6.0.1 | 9 / 19 | |
| 6.0.0 | 9 / 19 | |
| 5.0.0 | 9 / 19 | |
| 4.0.0 | 9 / 19 | |
| 3.2.0 | 9 / 19 | |
| 3.1.1 | 9 / 19 | |
| 3.1.0 | 9 / 19 | |
| 3.0.0 | 9 / 19 |
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.