@rango-dev/provider-metamask
MetaMask Wallet integration for hub. [Homepage](https://metamask.io/) | [Docs](https://docs.metamask.io/)
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package; sparse metadata is a consistent pattern across all @rango-dev wallet providers, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): No description is a stable pattern for this org's wallet provider packages; not indicative of malice. | ai | |
| dependencies | unvetted-dep:@rango-dev/signer-evm | AI (dependencies): Internal @rango-dev monorepo sibling dep; consistent across versions of this package. | ai | |
| dependencies | unvetted-dep:@rango-dev/signer-solana | AI (dependencies): Internal @rango-dev monorepo sibling dep; consistent across versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established rango-dev package with 274 versions; no provenance is consistent across all releases. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.60.0 | 7 / 3 | |
| 0.59.1 | 7 / 3 | |
| 0.59.0 | 7 / 3 | |
| 0.58.0 | 7 / 3 | |
| 0.57.0 | 7 / 3 | |
| 0.56.0 | 7 / 3 | |
| 0.55.0 | 7 / 3 | |
| 0.54.1 | 7 / 3 | |
| 0.52.0 | 7 / 3 | |
| 0.51.0 | 4 / 0 | |
| 0.50.0 | 4 / 0 | |
| 0.49.0 | 4 / 0 | |
| 0.48.0 | 3 / 0 | |
| 0.47.0 | 3 / 0 | |
| 0.46.0 | 3 / 0 | |
| 0.45.0 | 3 / 0 | |
| 0.44.1 | 3 / 0 | |
| 0.44.0 | 3 / 0 |
v0.60.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.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.
v0.51.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.
v0.50.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.
v0.49.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.
v0.48.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.
v0.47.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.
v0.46.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.
v0.45.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.
v0.44.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.
v0.44.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.