@ledgerhq/hw-app-cosmos
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): Old Ledger-internal maintainer swap, stable for years, no malicious activity since. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org transfer, not a takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher change from 2022, long-stable, matches Ledger org account. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 6.36.6 | 3 / 10 | |
| 6.36.5 | 3 / 10 | |
| 6.36.4 | 3 / 10 | |
| 6.36.3 | 3 / 10 | |
| 6.36.2 | 3 / 10 | |
| 6.36.1 | 3 / 10 | |
| 6.36.0 | 3 / 10 | |
| 6.35.1 | 3 / 10 | |
| 6.35.0 | 3 / 10 | |
| 6.34.0 | 3 / 10 | |
| 6.33.0 | 3 / 10 | |
| 6.32.12 | 3 / 9 | |
| 6.32.11 | 3 / 9 | |
| 6.32.10 | 3 / 9 | |
| 6.32.9 | 3 / 9 | |
| 6.32.8 | 3 / 9 | |
| 6.32.7 | 3 / 9 | |
| 6.32.6 | 3 / 9 | |
| 6.32.5 | 3 / 9 | |
| 6.32.4 | 3 / 9 | |
| 6.32.3 | 3 / 9 | |
| 6.32.2 | 3 / 10 | |
| 6.32.1 | 3 / 10 | |
| 6.32.0 | 3 / 10 | |
| 6.31.0 | 3 / 10 | |
| 6.30.4 | 3 / 9 | |
| 6.30.3 | 3 / 9 | |
| 6.30.2 | 3 / 9 | |
| 6.30.1 | 3 / 9 | |
| 6.30.0 | 3 / 9 | |
| 6.29.6 | 3 / 9 | |
| 6.29.5 | 3 / 9 | |
| 6.29.4 | 3 / 9 | |
| 6.29.3 | 3 / 9 | |
| 6.29.2 | 3 / 9 | |
| 6.29.1 | 3 / 9 | |
| 6.29.0 | 3 / 9 | |
| 6.28.6 | 3 / 9 | |
| 6.28.5 | 3 / 9 | |
| 6.28.4 | 3 / 9 | |
| 6.28.3 | 3 / 9 | |
| 6.28.2 | 3 / 9 | |
| 6.28.1 | 3 / 9 | |
| 6.28.0 | 3 / 9 | |
| 6.27.13 | 3 / 10 | |
| 6.27.12 | 3 / 1 | |
| 6.27.11 | 3 / 1 | |
| 6.27.10 | 3 / 1 | |
| 6.27.9 | 3 / 1 | |
| 6.27.8 | 3 / 1 | |
| 6.27.7 | 3 / 1 |
v6.36.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.36.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.30.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.30.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.29.6
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (juan-cortes) 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.
v6.29.5
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (juan-cortes) 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.
v6.29.4
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (juan-cortes) 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.
v6.29.3
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (juan-cortes) 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.
v6.29.2
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (juan-cortes) 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.
v6.29.1
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-12-12. It has since remained available on npm for 952 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.
v6.29.0
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-11-24. It has since remained available on npm for 970 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.
v6.28.6
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-11-09. It has since remained available on npm for 985 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.
v6.28.5
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-08-16. It has since remained available on npm for 1070 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.
v6.28.4
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-08-07. It has since remained available on npm for 1079 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.
v6.28.3
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-07-18. It has since remained available on npm for 1099 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.
v6.28.2
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-06-23. It has since remained available on npm for 1124 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.
v6.28.1
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-05-26. It has since remained available on npm for 1152 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.
v6.28.0
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-05-09. It has since remained available on npm for 1169 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.
v6.27.13
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-04-03. It has since remained available on npm for 1205 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.
v6.27.12
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-02-15. It has since remained available on npm for 1252 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.
v6.27.11
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-02-06. It has since remained available on npm for 1261 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.
v6.27.10
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-01-13. It has since remained available on npm for 1285 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.
v6.27.9
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-12-22. It has since remained available on npm for 1307 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.
v6.27.8
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-11-30. It has since remained available on npm for 1329 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.
v6.27.7
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-11-18. It has since remained available on npm for 1341 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.