@ledgerhq/wallet-api-core
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established org package; missing description is a cosmetic issue, not a risk signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata fields are structural, not indicative of spam. | ai | |
| dependencies | unvetted-dep:thor-devkit | AI (dependencies): thor-devkit is the official VeChain SDK; its use in a multi-chain wallet API core is expected and stable. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is a core primitive in blockchain/cryptocurrency libraries. Buffer.from(x, 'hex') in Bitcoin/Stacks serializers is standard and expected for this wallet API package. | ai | |
| dependencies | unvetted-dep:@stacks/transactions | AI (dependencies): @stacks/transactions is the official Stacks blockchain library; its use in a multi-chain wallet API core is expected and legitimate. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.31.0 | 6 / 10 | |
| 1.30.1 | 6 / 10 | |
| 1.30.0 | 6 / 10 | |
| 1.29.0 | 6 / 10 | |
| 1.28.0 | 6 / 10 | |
| 1.27.0 | 6 / 10 | |
| 1.26.1 | 6 / 10 | |
| 1.26.0 | 6 / 10 | |
| 1.25.0 | 7 / 10 | |
| 1.24.2 | 7 / 10 | |
| 1.24.1 | 7 / 10 | |
| 1.24.0 | 7 / 10 | |
| 1.23.0 | 7 / 10 | |
| 1.22.0 | 7 / 10 | |
| 1.21.1 | 7 / 10 | |
| 1.21.0 | 7 / 10 | |
| 1.20.0 | 7 / 10 |
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.