@ledgerhq/hw-app-solana
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Ledger org migrated to CI publisher account; consistent across package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old individual maintainers replaced by CI account, expected org-wide change. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable CI publisher (910d), not consistent with takeover. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used to pass trusted name data to Ledger hardware wallet transport; legitimate protocol usage for this package. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 7.10.6 | 3 / 11 | |
| 7.10.5 | 3 / 11 | |
| 7.10.4 | 3 / 11 | |
| 7.10.3 | 3 / 11 | |
| 7.10.2 | 3 / 11 | |
| 7.10.1 | 3 / 11 | |
| 7.10.0 | 3 / 11 | |
| 7.9.1 | 3 / 11 | |
| 7.9.0 | 3 / 11 | |
| 7.8.0 | 3 / 11 | |
| 7.7.0 | 3 / 11 | |
| 7.6.3 | 3 / 10 | |
| 7.6.2 | 3 / 10 | |
| 7.6.1 | 3 / 10 | |
| 7.6.0 | 3 / 10 | |
| 7.5.5 | 3 / 10 | |
| 7.5.4 | 3 / 10 | |
| 7.5.3 | 3 / 10 | |
| 7.5.2 | 3 / 10 | |
| 7.5.1 | 3 / 10 | |
| 7.5.0 | 3 / 10 | |
| 7.4.2 | 3 / 11 | |
| 7.4.1 | 3 / 11 | |
| 7.4.0 | 3 / 11 | |
| 7.3.0 | 3 / 11 | |
| 7.2.4 | 3 / 11 | |
| 7.2.3 | 3 / 11 | |
| 7.2.2 | 3 / 11 | |
| 7.2.1 | 3 / 11 | |
| 7.2.0 | 3 / 11 | |
| 7.1.6 | 3 / 11 | |
| 7.1.5 | 3 / 11 | |
| 7.1.4 | 3 / 11 | |
| 7.1.3 | 3 / 11 | |
| 7.1.2 | 3 / 11 | |
| 7.1.1 | 3 / 11 | |
| 7.1.0 | 3 / 11 | |
| 7.0.14 | 3 / 11 | |
| 7.0.13 | 4 / 11 | |
| 7.0.12 | 4 / 11 | |
| 7.0.11 | 4 / 11 | |
| 7.0.10 | 4 / 11 | |
| 7.0.9 | 4 / 11 | |
| 7.0.8 | 4 / 11 | |
| 7.0.7 | 4 / 12 | |
| 7.0.6 | 4 / 3 | |
| 7.0.5 | 4 / 3 | |
| 7.0.4 | 4 / 3 | |
| 7.0.3 | 4 / 3 | |
| 7.0.2 | 4 / 3 | |
| 7.0.1 | 4 / 3 |
v7.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.6
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-18. It has since remained available on npm for 824 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.
v7.1.5
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-03-19. It has since remained available on npm for 854 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.
v7.1.4
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-19. It has since remained available on npm for 883 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.
v7.1.3
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-31. It has since remained available on npm for 902 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.
v7.1.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-23. It has since remained available on npm for 910 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.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.