@rango-dev/provider-ready
Ready Wallet integration for hub. [Homepage](https://www.ready.tech/) | [Docs](https://docs.ready.tech/)
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/mod.js | AI (source-diff): dist/mod.js is a standard minified ESM bundle from the rango-dev build pipeline; not obfuscated malware. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this monorepo package; not a security signal on its own. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is consistent across the @rango-dev monorepo packages; not indicative of spam or malice. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.60.0 | 4 / 0 | |
| 0.59.1 | 4 / 0 | |
| 0.59.0 | 4 / 0 | |
| 0.58.0 | 4 / 0 | |
| 0.57.0 | 4 / 0 | |
| 0.56.0 | 4 / 0 | |
| 0.55.0 | 3 / 0 | |
| 0.54.1 | 3 / 0 | |
| 0.52.0 | 3 / 0 | |
| 0.51.0 | 3 / 0 | |
| 0.50.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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[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. Consider requesting the maintainer enable provenance via CI/CD.
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.