@metamask/perps-controller
Controller for perpetual trading functionality in MetaMask
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 to GitHub Actions CI/CD publishing with SLSA provenance; stable for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known MetaMask org members; legitimate team expansion. | ai | |
| 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 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 9.3.0 | 10 / 20 | |
| 9.2.1 | 10 / 20 | |
| 9.2.0 | 10 / 20 | |
| 9.1.0 | 10 / 20 | |
| 9.0.0 | 10 / 20 | |
| 8.3.0 | 10 / 19 | |
| 8.2.0 | 9 / 19 | |
| 8.1.0 | 9 / 19 | |
| 8.0.0 | 9 / 19 | |
| 7.0.0 | 9 / 19 | |
| 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 | |
| 2.0.0 | 10 / 18 | |
| 1.3.0 | 10 / 17 | |
| 1.2.0 | 10 / 17 | |
| 1.1.0 | 10 / 17 | |
| 1.0.1 | 10 / 17 | |
| 1.0.0 | 10 / 17 |
v9.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.
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.