@ledgerhq/coin-stellar
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is legitimately declared and used in this Ledger monorepo package; phantom-dep heuristic is a false positive for this context. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/devices | AI (phantom-deps): Same-org dependency declared and used in monorepo; phantom-dep heuristic does not apply to intra-org references. | ai | |
| dependencies | unvetted-dep:@exodus/patch-broken-hermes-typed-arrays | AI (dependencies): Known React Native/Hermes compatibility shim used in mobile wallet context; consistent with LedgerHQ's mobile app ecosystem needs. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in serialization.js is standard Stellar memo field handling (base64→hex conversion), not obfuscation or malicious payload processing. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:expect | AI (phantom-deps): expect is a test assertion library listed in dependencies; referenced in jest config. Not a phantom dependency risk for this package. | ai | |
| phantom-deps | phantom-dep:invariant | AI (phantom-deps): invariant is a standard utility listed in dependencies; referenced in config files. Not a phantom dependency risk for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 6.22.1 | 8 / 11 | |
| 6.22.0 | 9 / 11 | |
| 6.21.1 | 9 / 11 | |
| 6.21.0 | 9 / 11 | |
| 6.20.0 | 11 / 11 | |
| 6.19.0 | 12 / 9 | |
| 6.18.0 | 15 / 9 | |
| 6.17.0 | 14 / 9 | |
| 6.15.0 | 15 / 10 | |
| 6.14.0 | 15 / 10 | |
| 6.12.1 | 15 / 10 | |
| 6.12.0 | 15 / 10 | |
| 6.11.0 | 15 / 10 | |
| 6.10.0 | 15 / 9 | |
| 6.9.1 | 15 / 9 | |
| 6.9.0 | 15 / 9 | |
| 6.8.1 | 15 / 9 | |
| 6.8.0 | 15 / 9 | |
| 6.7.0 | 15 / 9 | |
| 6.6.0 | 15 / 9 | |
| 6.4.0 | 15 / 9 | |
| 6.1.0 | 15 / 9 | |
| 6.0.0 | 15 / 9 |
v6.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.