@ledgerhq/coin-multiversx
Ledger MultiversX Coin integration
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:protobufjs | AI (dependencies): protobufjs is a standard serialization library legitimately used for blockchain protocol encoding in this MultiversX coin integration. | ai | |
| dependencies | unvetted-dep:@multiversx/sdk-core | AI (dependencies): @multiversx/sdk-core is the official MultiversX blockchain SDK, a core dependency for this coin integration package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is explicitly declared as a direct dependency (1.13.2) in package.json; phantom-dep finding is a false positive. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used to decode MultiversX ESDT token identifiers — standard blockchain data handling, not obfuscation or malicious payload construction. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/live-promise | AI (phantom-deps): live-promise is explicitly declared as a direct dependency in package.json; phantom-dep finding is a false positive. | ai | |
| phantom-deps | phantom-dep:protobufjs | AI (phantom-deps): protobufjs is explicitly declared as a direct dependency in package.json; phantom-dep finding is a false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is a utility function for binary data handling in a blockchain integration library; no suspicious payload construction. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 19 / 12 | |
| 0.19.0 | 20 / 10 | |
| 0.18.0 | 20 / 10 | |
| 0.17.4 | 20 / 10 | |
| 0.17.3 | 20 / 10 | |
| 0.17.2 | 20 / 10 | |
| 0.17.1 | 20 / 10 | |
| 0.17.0 | 20 / 10 | |
| 0.16.2 | 20 / 10 | |
| 0.16.1 | 20 / 10 | |
| 0.16.0 | 20 / 10 | |
| 0.15.0 | 20 / 10 | |
| 0.14.1 | 20 / 8 | |
| 0.14.0 | 20 / 8 | |
| 0.13.0 | 19 / 8 | |
| 0.12.0 | 19 / 8 | |
| 0.11.2 | 19 / 7 | |
| 0.11.1 | 19 / 7 | |
| 0.11.0 | 19 / 7 | |
| 0.10.3 | 19 / 7 | |
| 0.10.2 | 19 / 7 | |
| 0.10.1 | 19 / 7 | |
| 0.10.0 | 19 / 7 | |
| 0.9.2 | 19 / 6 | |
| 0.9.1 | 19 / 6 | |
| 0.9.0 | 19 / 6 | |
| 0.8.2 | 19 / 6 | |
| 0.8.1 | 19 / 6 | |
| 0.8.0 | 19 / 6 | |
| 0.7.0 | 19 / 6 | |
| 0.6.0 | 19 / 6 | |
| 0.5.3 | 19 / 6 | |
| 0.5.2 | 19 / 6 | |
| 0.5.1 | 19 / 6 | |
| 0.5.0 | 19 / 6 | |
| 0.4.18 | 19 / 6 | |
| 0.4.17 | 19 / 6 | |
| 0.4.16 | 19 / 6 | |
| 0.4.15 | 19 / 6 | |
| 0.4.14 | 19 / 6 | |
| 0.4.13 | 19 / 6 | |
| 0.4.12 | 19 / 6 | |
| 0.4.11 | 19 / 6 | |
| 0.4.10 | 19 / 6 | |
| 0.4.9 | 19 / 6 | |
| 0.4.8 | 19 / 7 | |
| 0.4.7 | 19 / 7 | |
| 0.4.6 | 19 / 7 | |
| 0.4.5 | 19 / 7 | |
| 0.4.4 | 19 / 6 | |
| 0.4.3 | 19 / 6 | |
| 0.4.2 | 19 / 6 | |
| 0.4.1 | 19 / 6 | |
| 0.4.0 | 19 / 6 | |
| 0.3.0 | 19 / 6 | |
| 0.2.2 | 19 / 5 | |
| 0.2.1 | 19 / 5 | |
| 0.2.0 | 19 / 5 |
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
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.