@rango-dev/provider-coinbase
Coinbase Wallet integration for hub. [Homepage](https://www.coinbase.com/wallet) | [Docs](https://docs.cdp.coinbase.com/wallet-sdk/docs/welcome)
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@hub3js/evm | AI (dependencies): First-party Rango 'Hub' framework by same publisher; typed evm actions/builders only. | ai | |
| dependencies | unvetted-dep:@hub3js/core | AI (dependencies): First-party Rango 'Hub' framework by same publisher (yeager-eren); used only as typed provider builder. | ai | |
| dependencies | unvetted-dep:@hub3js/solana | AI (dependencies): First-party Rango 'Hub' framework by same publisher; typed solana actions/builders only. | ai | |
| dependencies | unvetted-dep:@hub3js/std | AI (dependencies): First-party Rango 'Hub' framework by same publisher; benign operators/builders only. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across the package's long history; not a malware signal for this scoped package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata is a known pattern for @rango-dev scoped packages across 291 versions. | ai | |
| dependencies | unvetted-dep:@rango-dev/signer-solana | AI (dependencies): Internal @rango-dev scoped dep, consistent with this package's ecosystem pattern across versions. | ai | |
| dependencies | unvetted-dep:@rango-dev/signer-evm | AI (dependencies): Internal @rango-dev scoped dep, consistent with this package's ecosystem pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Rango-dev packages consistently lack provenance; stable false positive for this publisher family. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 0.62.0 | 10 / 0 | |
| 0.61.0 | 6 / 0 | |
| 0.60.1 | 6 / 0 | |
| 0.60.0 | 6 / 0 | |
| 0.59.0 | 6 / 0 | |
| 0.58.0 | 6 / 0 | |
| 0.57.0 | 6 / 0 | |
| 0.56.0 | 6 / 0 | |
| 0.55.1 | 6 / 0 | |
| 0.53.0 | 6 / 0 | |
| 0.52.0 | 6 / 0 | |
| 0.51.0 | 6 / 0 | |
| 0.50.0 | 6 / 0 | |
| 0.49.0 | 5 / 0 | |
| 0.48.0 | 5 / 0 | |
| 0.47.0 | 5 / 0 | |
| 0.46.0 | 5 / 0 | |
| 0.45.1 | 5 / 0 | |
| 0.45.0 | 5 / 0 | |
| 0.44.0 | 5 / 0 | |
| 0.43.0 | 5 / 0 | |
| 0.42.0 | 5 / 0 | |
| 0.41.0 | 5 / 0 | |
| 0.40.0 | 5 / 0 | |
| 0.39.0 | 5 / 0 | |
| 0.38.0 | 5 / 0 | |
| 0.37.0 | 4 / 0 | |
| 0.36.0 | 4 / 0 | |
| 0.35.1 | 4 / 0 | |
| 0.35.0 | 4 / 0 | |
| 0.34.0 | 4 / 0 | |
| 0.33.2 | 4 / 0 | |
| 0.33.1 | 4 / 0 | |
| 0.33.0 | 4 / 0 | |
| 0.32.0 | 4 / 0 | |
| 0.31.0 | 4 / 0 | |
| 0.30.0 | 4 / 0 | |
| 0.29.0 | 4 / 0 | |
| 0.28.0 | 4 / 0 | |
| 0.27.0 | 4 / 0 | |
| 0.26.0 | 4 / 0 | |
| 0.25.0 | 4 / 0 | |
| 0.24.0 | 4 / 0 | |
| 0.23.0 | 4 / 0 | |
| 0.22.0 | 4 / 0 | |
| 0.21.0 | 4 / 0 | |
| 0.20.0 | 4 / 0 | |
| 0.19.0 | 4 / 0 | |
| 0.18.0 | 4 / 0 | |
| 0.17.0 | 4 / 0 | |
| 0.16.0 | 4 / 0 | |
| 0.15.0 | 4 / 0 | |
| 0.14.0 | 4 / 0 | |
| 0.13.0 | 4 / 0 | |
| 0.12.0 | 4 / 0 | |
| 0.11.0 | 4 / 0 | |
| 0.10.0 | 4 / 0 | |
| 0.9.0 | 4 / 0 | |
| 0.8.0 | 4 / 0 | |
| 0.7.0 | 4 / 0 | |
| 0.6.0 | 4 / 0 | |
| 0.5.0 | 4 / 0 | |
| 0.4.0 | 4 / 0 | |
| 0.3.0 | 4 / 0 | |
| 0.2.0 | 4 / 0 | |
| 0.1.15 | 4 / 0 | |
| 0.1.14 | 4 / 0 | |
| 0.1.13 | 4 / 0 | |
| 0.1.12 | 4 / 0 | |
| 0.1.11 | 4 / 0 |
v0.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.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.33.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.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.