@zondax/ledger-live-icp
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/browser/utils/validations.js | AI (source-diff): esbuild browser bundle; same boilerplate pattern. | ai | |
| source-diff | net-exec-file:dist/browser/utils/subAccount.js | AI (source-diff): esbuild polyfill boilerplate, not malware. | ai | |
| source-diff | obfuscated-file:dist/browser/utils/subAccount.js | AI (source-diff): esbuild browser bundle; same boilerplate pattern. | ai | |
| source-diff | net-exec-file:dist/browser/utils/signing.js | AI (source-diff): esbuild polyfill boilerplate, not malware. | ai | |
| source-diff | net-exec-file:dist/browser/utils/index.js | AI (source-diff): esbuild polyfill boilerplate, not malware. | ai | |
| source-diff | obfuscated-file:dist/browser/utils/signing.js | AI (source-diff): esbuild browser bundle; same boilerplate pattern. | ai | |
| source-diff | obfuscated-file:dist/browser/utils/pubKey.js | AI (source-diff): esbuild browser bundle; same boilerplate pattern. | ai | |
| source-diff | net-exec-file:dist/browser/neurons/neuronData.js | AI (source-diff): esbuild polyfill boilerplate, not malware. | ai | |
| source-diff | obfuscated-file:dist/browser/neurons/neuronData.js | AI (source-diff): esbuild browser bundle; same boilerplate pattern. | ai | |
| source-diff | obfuscated-file:dist/browser/neurons/calculations.js | AI (source-diff): esbuild browser bundle with inlined deps; standard minified output, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/browser/neurons/calculations.js | AI (source-diff): Network/exec pattern is esbuild polyfill boilerplate, not malware. | ai | |
| source-diff | obfuscated-file:dist/browser/neurons/consts.js | AI (source-diff): esbuild browser bundle; same boilerplate pattern. | ai | |
| source-diff | obfuscated-file:dist/browser/utils/hash.js | AI (source-diff): esbuild browser bundle; same boilerplate pattern. | ai | |
| source-diff | net-exec-file:dist/browser/utils/hash.js | AI (source-diff): esbuild polyfill boilerplate, not malware. | ai | |
| source-diff | net-exec-file:dist/browser/index.js | AI (source-diff): esbuild polyfill boilerplate, not malware. | ai | |
| source-diff | net-exec-file:dist/browser/neurons/index.js | AI (source-diff): esbuild polyfill boilerplate, not malware. | ai | |
| phantom-deps | phantom-dep:@noble/hashes | AI (phantom-deps): Bundled transitive dep; phantom detection false positive. | ai | |
| source-diff | encoded-string-file:dist/esm/nns.js | AI (source-diff): Same IC root key constant bundled from @dfinity/agent. | ai | |
| source-diff | obfuscated-file:dist/browser/index.js | AI (source-diff): Standard esbuild browser bundle with source maps; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/browser/neurons/index.js | AI (source-diff): Standard esbuild browser bundle with source maps; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/browser/utils/index.js | AI (source-diff): Standard esbuild browser bundle with source maps; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/browser/nns.js | AI (source-diff): Standard esbuild browser bundle with source maps; not obfuscated. | ai | |
| source-diff | encoded-string-file:dist/cjs/agent.js | AI (source-diff): Long hex string is the public IC root key constant from @dfinity/agent, not a payload. | ai | |
| source-diff | encoded-string-file:dist/esm/agent.js | AI (source-diff): Same IC root key constant; stable false positive for this package. | ai | |
| source-diff | encoded-string-file:dist/cjs/index.js | AI (source-diff): Same IC root key constant bundled from @dfinity/agent. | ai | |
| source-diff | encoded-string-file:dist/cjs/neurons/index.js | AI (source-diff): Same IC root key constant bundled from @dfinity/agent. | ai | |
| source-diff | encoded-string-file:dist/cjs/utils/index.js | AI (source-diff): Same IC root key constant bundled from @dfinity/agent. | ai | |
| source-diff | encoded-string-file:dist/esm/index.js | AI (source-diff): Same IC root key constant bundled from @dfinity/agent. | ai | |
| source-diff | encoded-string-file:dist/esm/utils/index.js | AI (source-diff): Same IC root key constant bundled from @dfinity/agent. | ai | |
| source-diff | encoded-string-file:dist/cjs/nns.js | AI (source-diff): Same IC root key constant bundled from @dfinity/agent. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase due to new browser bundle targets inlining @dfinity/* deps; expected for this package type. | ai | |
| phantom-deps | phantom-dep:invariant | AI (phantom-deps): Used as a bundled dep; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:browser-env | AI (phantom-deps): Referenced in config/test setup; phantom detection false positive. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used for ICP certificate/protocol data parsing; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:esbuild-plugin-import-pattern | AI (phantom-deps): Build tool used in esbuild config; leaked into runtime deps but poses no security risk for this package. | ai | |
| dependencies | unvetted-dep:@dfinity/identity-secp256k1 | AI (dependencies): Official DFINITY Foundation identity package; expected for hardware wallet integrations. | ai | |
| dependencies | unvetted-dep:@dfinity/ledger-icp | AI (dependencies): Official DFINITY Foundation ICP ledger package; core dependency for this bridge library. | ai | |
| dependencies | unvetted-dep:@dfinity/principal | AI (dependencies): Official DFINITY Foundation principal package; canonical ICP dependency. | ai | |
| dependencies | unvetted-dep:@dfinity/candid | AI (dependencies): Official DFINITY Foundation Candid serialization package; canonical ICP dependency. | ai | |
| dependencies | unvetted-dep:@dfinity/utils | AI (dependencies): Official DFINITY Foundation utilities package; expected for ICP integrations. | ai | |
| dependencies | unvetted-dep:@dfinity/nns | AI (dependencies): Official DFINITY Foundation package for ICP NNS integration; expected dependency for any ICP bridge library. | ai | |
| dependencies | unvetted-dep:@dfinity/agent | AI (dependencies): Official DFINITY Foundation agent package; canonical dependency for ICP ecosystem integrations. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.4.2 | 12 / 18 | |
| 1.4.1 | 12 / 18 | |
| 1.4.0 | 13 / 19 | |
| 1.3.1 | 15 / 18 | |
| 1.3.0 | 15 / 18 | |
| 1.2.2 | 13 / 17 | |
| 1.2.1 | 12 / 17 | |
| 1.2.0 | 12 / 17 | |
| 1.1.1 | 12 / 15 | |
| 1.1.0 | 12 / 14 | |
| 1.0.1 | 11 / 11 | |
| 1.0.0 | 11 / 11 |
v1.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
23 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
23 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
17 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
14 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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
14 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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
10 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.