@rango-dev/provider-bitget
Bitget Wallet integration for hub. [Homepage](https://web3.bitget.com/) | [Docs](https://web3.bitget.com/en/wallet/developer)
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 sub-package; missing metadata is a known pattern for @rango-dev workspace packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @rango-dev monorepo publishing pattern across 196 versions. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding PSBT from base64 to hex is standard Bitcoin transaction handling, not a malicious payload. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.57.0 | 5 / 0 | |
| 0.56.1 | 5 / 0 | |
| 0.56.0 | 5 / 0 | |
| 0.55.0 | 5 / 0 | |
| 0.54.0 | 5 / 0 | |
| 0.53.0 | 5 / 0 | |
| 0.52.0 | 5 / 0 | |
| 0.51.1 | 5 / 0 | |
| 0.49.0 | 5 / 0 | |
| 0.48.0 | 5 / 0 | |
| 0.47.0 | 5 / 0 | |
| 0.46.0 | 5 / 0 | |
| 0.45.0 | 4 / 0 | |
| 0.44.0 | 4 / 0 | |
| 0.43.0 | 4 / 0 | |
| 0.42.0 | 4 / 0 | |
| 0.41.1 | 4 / 0 | |
| 0.41.0 | 4 / 0 |
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.