@rango-dev/provider-braavos
Braavos Wallet integration for hub. [Homepage](https://braavos.app/) | [Docs](https://docs.braavos.app/)
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 build artifact; content is readable wallet integration code, not obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 206 versions; publisher hasn't enabled Sigstore provenance — stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established @rango-dev monorepo package; sparse metadata is a style choice, not spam. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.54.0 | 4 / 0 | |
| 0.53.1 | 4 / 0 | |
| 0.53.0 | 4 / 0 | |
| 0.52.0 | 4 / 0 | |
| 0.51.0 | 4 / 0 | |
| 0.50.0 | 4 / 0 | |
| 0.49.0 | 3 / 0 | |
| 0.48.1 | 3 / 0 | |
| 0.46.0 | 3 / 0 | |
| 0.45.0 | 3 / 0 | |
| 0.44.0 | 3 / 0 | |
| 0.43.0 | 3 / 0 | |
| 0.42.0 | 3 / 0 | |
| 0.41.0 | 3 / 0 | |
| 0.40.0 | 3 / 0 | |
| 0.39.0 | 3 / 0 | |
| 0.38.1 | 3 / 0 | |
| 0.38.0 | 3 / 0 |
v0.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.50.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.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.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.46.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.45.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.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.38.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.