@metamask/transaction-pay-controller
Manages alternate payment strategies to provide required funds for transactions 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 from metamaskbot to GitHub Actions CI; SLSA provenance confirms legitimate pipeline. | ai | |
| phantom-deps | phantom-dep:@ethersproject/contracts | AI (phantom-deps): Declared dep referenced in config, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@ethersproject/providers | AI (phantom-deps): Declared dep referenced in config, not directly imported; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): MetaMask monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): bn.js is declared in package.json dependencies and used transitively; phantom-dep false positive for this package. | ai |
Versions (showing 51 of 91)
| Version | Deps | Published |
|---|---|---|
| 23.5.1 | 22 / 10 | |
| 23.5.0 | 22 / 10 | |
| 23.4.0 | 22 / 10 | |
| 23.3.1 | 22 / 10 | |
| 23.3.0 | 22 / 10 | |
| 23.2.0 | 22 / 10 | |
| 23.1.0 | 21 / 10 | |
| 23.0.0 | 21 / 10 | |
| 22.8.0 | 21 / 10 | |
| 22.7.0 | 21 / 10 | |
| 22.6.3 | 21 / 10 | |
| 22.6.2 | 21 / 10 | |
| 22.6.1 | 21 / 10 | |
| 22.6.0 | 21 / 10 | |
| 22.5.0 | 21 / 10 | |
| 22.4.0 | 21 / 10 | |
| 22.3.1 | 21 / 10 | |
| 22.3.0 | 21 / 10 | |
| 22.2.0 | 21 / 10 | |
| 22.1.0 | 21 / 10 | |
| 22.0.2 | 21 / 10 | |
| 22.0.1 | 21 / 10 | |
| 22.0.0 | 21 / 10 | |
| 21.1.0 | 21 / 10 | |
| 21.0.0 | 21 / 10 | |
| 20.2.0 | 21 / 10 | |
| 20.1.0 | 21 / 10 | |
| 20.0.1 | 21 / 10 | |
| 20.0.0 | 21 / 10 | |
| 19.3.0 | 21 / 10 | |
| 19.2.2 | 21 / 10 | |
| 19.2.1 | 21 / 10 | |
| 19.2.0 | 21 / 10 | |
| 19.1.3 | 21 / 10 | |
| 19.1.2 | 21 / 10 | |
| 19.1.1 | 21 / 10 | |
| 19.1.0 | 21 / 10 | |
| 19.0.3 | 21 / 10 | |
| 19.0.2 | 21 / 10 | |
| 19.0.1 | 21 / 10 | |
| 19.0.0 | 21 / 10 | |
| 18.2.0 | 21 / 10 | |
| 18.1.0 | 21 / 10 | |
| 18.0.0 | 20 / 10 | |
| 17.1.0 | 20 / 10 | |
| 17.0.0 | 20 / 9 | |
| 16.5.0 | 19 / 9 | |
| 16.4.1 | 19 / 9 | |
| 16.4.0 | 19 / 9 | |
| 16.3.0 | 19 / 9 | |
| 16.2.0 | 19 / 9 |
v23.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.3.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.