@ledgerhq/hw-transport-webusb
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): Stale publisher change from years ago, consistent across many prior approved versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Part of same long-stable Ledger team transition. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Change is 1455 days old and stable; not indicative of takeover. | ai |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 6.35.0 | 4 / 10 | |
| 6.34.4 | 4 / 10 | |
| 6.34.3 | 4 / 10 | |
| 6.34.2 | 4 / 10 | |
| 6.34.1 | 4 / 10 | |
| 6.34.0 | 4 / 10 | |
| 6.33.0 | 4 / 10 | |
| 6.32.0 | 4 / 10 | |
| 6.31.0 | 4 / 10 | |
| 6.30.0 | 4 / 10 | |
| 6.29.16 | 4 / 9 | |
| 6.29.15 | 4 / 9 | |
| 6.29.14 | 4 / 9 | |
| 6.29.13 | 4 / 9 | |
| 6.29.12 | 4 / 9 | |
| 6.29.11 | 4 / 9 | |
| 6.29.10 | 4 / 9 | |
| 6.29.9 | 4 / 9 | |
| 6.29.8 | 4 / 9 | |
| 6.29.7 | 4 / 9 | |
| 6.29.6 | 4 / 9 | |
| 6.29.5 | 4 / 9 | |
| 6.29.4 | 4 / 9 | |
| 6.29.3 | 4 / 9 | |
| 6.29.2 | 4 / 9 | |
| 6.29.1 | 4 / 9 | |
| 6.29.0 | 4 / 9 | |
| 6.28.6 | 4 / 9 | |
| 6.28.5 | 4 / 9 | |
| 6.28.4 | 4 / 9 | |
| 6.28.3 | 4 / 9 | |
| 6.28.2 | 4 / 9 | |
| 6.28.1 | 4 / 9 | |
| 6.28.0 | 4 / 9 | |
| 6.27.20 | 4 / 9 | |
| 6.27.19 | 4 / 9 | |
| 6.27.18 | 4 / 9 | |
| 6.27.17 | 4 / 9 | |
| 6.27.16 | 4 / 9 | |
| 6.27.15 | 4 / 9 | |
| 6.27.14 | 4 / 9 | |
| 6.27.13 | 4 / 10 | |
| 6.27.12 | 4 / 1 | |
| 6.27.11 | 4 / 1 | |
| 6.27.10 | 4 / 1 | |
| 6.27.9 | 4 / 1 | |
| 6.27.8 | 4 / 1 | |
| 6.27.7 | 4 / 1 | |
| 6.27.6 | 4 / 1 | |
| 6.27.5 | 4 / 1 | |
| 6.27.4 | 4 / 1 |
v6.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.28.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 825 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 (ldg-github-ci) than the most recent previously approved version (juan-cortes) on 2024-03-19. It has since remained available on npm for 855 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 (ldg-github-ci) than the most recent previously approved version (juan-cortes) on 2024-02-19. It has since remained available on npm for 884 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 (ldg-github-ci) than the most recent previously approved version (juan-cortes) on 2024-01-31. It has since remained available on npm for 903 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 (ldg-github-ci) than the most recent previously approved version (juan-cortes) on 2024-01-23. It has since remained available on npm for 911 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-12-12. It has since remained available on npm for 953 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-11-24. It has since remained available on npm for 971 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.20
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 986 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.19
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 1071 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.18
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 1080 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.17
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 1100 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.16
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 1125 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.15
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 1153 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.14
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 1170 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 1206 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 1253 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 1262 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 1286 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 1308 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 1330 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 1342 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.6
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-09-30. It has since remained available on npm for 1391 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.5
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-09-28. It has since remained available on npm for 1393 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.4
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-09-14. It has since remained available on npm for 1407 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.