@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, 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Legit org CI migration, stable across many versions since 2024. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale change 915d old, unchanged vs prior approved version. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same migration event, no takeover indicators. | ai | |
| 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 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 1.35.0 | 5 / 9 | |
| 1.34.0 | 5 / 9 | |
| 1.33.0 | 5 / 9 | |
| 1.32.1 | 5 / 9 | |
| 1.32.0 | 5 / 9 | |
| 1.31.1 | 5 / 9 | |
| 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 | |
| 1.19.1 | 7 / 10 | |
| 1.19.0 | 7 / 10 | |
| 1.18.0 | 4 / 12 | |
| 1.17.1 | 4 / 12 | |
| 1.17.0 | 4 / 12 | |
| 1.16.0 | 4 / 12 | |
| 1.15.0 | 4 / 12 | |
| 1.14.0 | 4 / 12 | |
| 1.13.0 | 4 / 12 | |
| 1.12.0 | 4 / 12 | |
| 1.11.0 | 4 / 12 | |
| 1.10.1 | 4 / 12 | |
| 1.10.0 | 4 / 12 | |
| 1.9.0 | 4 / 12 | |
| 1.8.0 | 4 / 11 | |
| 1.7.2 | 4 / 10 | |
| 1.7.1 | 4 / 10 | |
| 1.7.0 | 4 / 10 | |
| 1.6.2 | 4 / 10 | |
| 1.6.1 | 4 / 10 | |
| 1.6.0 | 4 / 10 | |
| 1.5.0 | 4 / 10 | |
| 1.4.0 | 4 / 10 | |
| 1.3.1 | 4 / 10 | |
| 1.3.0 | 4 / 10 | |
| 1.2.0 | 4 / 10 | |
| 1.1.0 | 4 / 10 | |
| 1.0.2 | 4 / 10 |
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-04-04. It has since remained available on npm for 838 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-04-02. It has since remained available on npm for 840 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-02-20. It has since remained available on npm for 881 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-02-14. It has since remained available on npm for 888 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-02-05. It has since remained available on npm for 896 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-01-19. It has since remained available on npm for 913 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-01-18. It has since remained available on npm for 915 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.