@rango-dev/provider-okx
OKX Wallet integration for hub. [Homepage](https://www.okx.com/web3) | [Docs](https://www.okx.com/web3/build/docs)
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): Monorepo sub-package in @rango-dev scope; sparse metadata is a consistent pattern across all 292 versions, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across all versions of this monorepo package; not a risk signal. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used for PSBT (Bitcoin transaction) hex conversion in a UTXO signer — standard cryptographic workflow. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.61.0 | 5 / 0 | |
| 0.60.1 | 5 / 0 | |
| 0.60.0 | 5 / 0 | |
| 0.59.0 | 5 / 0 | |
| 0.58.0 | 5 / 0 | |
| 0.57.0 | 5 / 0 | |
| 0.56.0 | 5 / 0 | |
| 0.55.1 | 5 / 0 | |
| 0.53.0 | 5 / 0 | |
| 0.52.0 | 5 / 0 | |
| 0.51.0 | 5 / 0 | |
| 0.50.0 | 5 / 0 | |
| 0.49.0 | 4 / 0 | |
| 0.48.0 | 4 / 0 | |
| 0.47.0 | 4 / 0 | |
| 0.46.0 | 4 / 0 | |
| 0.45.1 | 4 / 0 | |
| 0.45.0 | 4 / 0 |
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.55.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.