@metamask/connect-multichain
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:@metamask/onboarding | AI (dependencies): Official MetaMask package; ecosystem-consistent dependency. | ai | |
| dependencies | unvetted-dep:@metamask/rpc-errors | AI (dependencies): Official MetaMask package; ecosystem-consistent dependency. | ai | |
| dependencies | unvetted-dep:@metamask/multichain-ui | AI (dependencies): Official MetaMask package; ecosystem-consistent dependency. | ai | |
| dependencies | unvetted-dep:@metamask/multichain-api-client | AI (dependencies): Official MetaMask package; ecosystem-consistent dependency. | ai | |
| dependencies | unvetted-dep:@metamask/mobile-wallet-protocol-core | AI (dependencies): Official MetaMask package; ecosystem-consistent dependency. | ai | |
| dependencies | unvetted-dep:@metamask/mobile-wallet-protocol-dapp-client | AI (dependencies): Official MetaMask package; ecosystem-consistent dependency. | ai | |
| dependencies | unvetted-dep:@paulmillr/qr | AI (dependencies): QR code library by known author paulmillr; low-risk utility dependency. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 17 / 17 | |
| 0.14.0 | 17 / 17 | |
| 0.13.0 | 17 / 17 | |
| 0.12.1 | 17 / 17 | |
| 0.12.0 | 17 / 17 | |
| 0.11.1 | 17 / 17 | |
| 0.1.0 | 15 / 16 |
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.