@rango-dev/provider-rabby
Rabby Wallet integration for hub. [Homepage](https://rabby.io/) | [Docs](https://rabby.io/docs/integrating-rabby-wallet)
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 project's own build toolchain; content is fully readable wallet integration code. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 134 versions; monorepo publish pattern without Sigstore CI integration. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of a large monorepo ecosystem (133 versions); sparse metadata is a consistent pattern across @rango-dev/* packages, not a spam indicator. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.27.0 | 4 / 0 | |
| 0.26.1 | 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.1 | 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 | 3 / 0 | |
| 0.14.0 | 3 / 0 | |
| 0.13.0 | 3 / 0 | |
| 0.12.0 | 3 / 0 | |
| 0.11.1 | 3 / 0 | |
| 0.11.0 | 3 / 0 |
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.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.17.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.16.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.15.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.14.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.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.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.