@rango-dev/provider-ledger
Ledger integration for hub. [Homepage](https://www.ledger.com/) | [Docs](https://developers.ledger.com/)
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/Eth-HZ7OYD6G.js | AI (source-diff): Bundled esbuild output with visible library source, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/Eth-L5TO7MTO.js | AI (source-diff): esbuild bundled output (BN/semver libs), not obfuscation; stable build artifact. | ai | |
| source-diff | obfuscated-file:dist/TransportWebHID-MELLZRNW.js | AI (source-diff): Bundled WebHID transport + semver dep code, minified build output. | ai | |
| source-diff | obfuscated-file:dist/Eth-U7JYAA6P.js | AI (source-diff): Bundled Ledger/ethers/BN.js dependency code, not true obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Explained by bundling previously-external deps per build script. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): First-party @rango-dev sibling package, not unvetted. | ai | |
| source-diff | obfuscated-file:dist/mod.js | AI (source-diff): Bundled main entry importing first-party rango-dev packages. | ai | |
| source-diff | obfuscated-file:dist/Eth-Y5JFGVQA.js | AI (source-diff): Bundled esbuild output of BN.js/ledger deps, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/Solana-UB4SGWQ3.js | AI (source-diff): Bundled esbuild output of Ledger Solana app lib. | ai | |
| source-diff | obfuscated-file:dist/TransportWebHID-JLT4ETY3.js | AI (source-diff): Bundled esbuild output including semver, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse metadata is consistent across all @rango-dev/* packages, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/types-cryptoassets | AI (phantom-deps): Type-only package referenced in build config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/types-devices | AI (phantom-deps): Type-only package referenced in config/build; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/w3c-web-hid | AI (phantom-deps): Type-only package used for HID API typings; not directly imported at runtime by convention. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.32.0 | 19 / 0 | |
| 0.31.0 | 14 / 0 | |
| 0.30.1 | 14 / 0 | |
| 0.30.0 | 14 / 0 | |
| 0.29.0 | 14 / 0 | |
| 0.28.0 | 14 / 0 | |
| 0.27.0 | 14 / 0 | |
| 0.26.0 | 14 / 0 | |
| 0.25.1 | 14 / 0 | |
| 0.23.0 | 14 / 0 | |
| 0.7.1 | 13 / 0 | |
| 0.6.0 | 10 / 0 | |
| 0.5.1 | 10 / 0 | |
| 0.5.0 | 10 / 0 | |
| 0.4.0 | 10 / 0 | |
| 0.3.0 | 10 / 0 | |
| 0.2.0 | 5 / 0 |
v0.32.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.