← Home

@ledgerhq/errors

49
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

phenry-ledgersergii-shkolingbrahm-ledgerthomas.coudrayldg-github-civbouzonledger-releaser

Keywords

Ledger

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Long-stale transition on a trusted, high-usage Ledger package; no malicious behavior evident. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with team turnover, not takeover, given 1453-day stability. ai
provenance publisher-changed-stale AI (provenance): Publisher change is old and stable, inconsistent with account compromise. ai

Versions (showing 49 of 49)

Version Deps Published
6.37.0 0 / 9
6.36.0 0 / 9
6.35.0 0 / 9
6.34.1 0 / 9
6.34.0 0 / 9
6.33.0 0 / 9
6.32.0 0 / 9
6.31.0 0 / 9
6.30.0 0 / 9
6.29.0 0 / 9
6.28.0 0 / 8
6.27.1 0 / 8
6.27.0 0 / 8
6.26.0 0 / 8
6.25.0 0 / 8
6.24.0 0 / 8
6.23.0 0 / 8
6.22.0 0 / 8
6.21.0 0 / 8
6.19.1 0 / 8
6.19.0 0 / 8
6.18.0 0 / 8
6.17.0 0 / 8
6.16.4 0 / 8
6.16.3 0 / 8
6.16.2 0 / 8
6.16.1 0 / 8
6.16.0 0 / 8
6.15.0 0 / 8
6.14.0 0 / 8
6.13.1 0 / 8
6.13.0 0 / 8
6.12.7 0 / 8
6.12.6 0 / 8
6.12.5 0 / 8
6.12.4 0 / 9
6.12.3 0 / 0
6.12.2 0 / 0
6.12.1 0 / 0
6.12.0 0 / 0
6.11.1 0 / 0
6.11.0 0 / 0
6.10.2 0 / 0
6.10.1 0 / 0
6.10.0 0 / 0
6.2.0 0 / 0
6.0.2 0 / 0
6.0.1 0 / 0
6.0.0 0 / 0

v6.37.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.19.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.19.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.18.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.17.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.16.4

2 findings
MEDIUM Publisher changed: gre → ldg-github-ci (on 2024-04-18, unremoved on npm for 823d) provenance

This version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (gre) on 2024-04-18. It has since remained available on npm for 823 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.16.3

2 findings
MEDIUM Publisher changed: gre → ldg-github-ci (on 2024-03-19, unremoved on npm for 853d) provenance

This version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (gre) on 2024-03-19. It has since remained available on npm for 853 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.16.2

2 findings
MEDIUM Publisher changed: gre → ldg-github-ci (on 2024-02-19, unremoved on npm for 882d) provenance

This version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (gre) on 2024-02-19. It has since remained available on npm for 882 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.16.1

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-12-12, unremoved on npm for 951d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-12-12. It has since remained available on npm for 951 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.16.0

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-11-24, unremoved on npm for 969d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-11-24. It has since remained available on npm for 969 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.15.0

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-11-09, unremoved on npm for 984d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-11-09. It has since remained available on npm for 984 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.14.0

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-08-16, unremoved on npm for 1069d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-08-16. It has since remained available on npm for 1069 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.13.1

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-08-07, unremoved on npm for 1078d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-08-07. It has since remained available on npm for 1078 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.13.0

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-07-18, unremoved on npm for 1098d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-07-18. It has since remained available on npm for 1098 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.12.7

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-06-23, unremoved on npm for 1123d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-06-23. It has since remained available on npm for 1123 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.12.6

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-05-26, unremoved on npm for 1151d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-05-26. It has since remained available on npm for 1151 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.12.5

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-05-09, unremoved on npm for 1168d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-05-09. It has since remained available on npm for 1168 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.12.4

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-04-03, unremoved on npm for 1204d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-04-03. It has since remained available on npm for 1204 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.12.3

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2023-01-13, unremoved on npm for 1284d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-01-13. It has since remained available on npm for 1284 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.12.2

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2022-12-22, unremoved on npm for 1306d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2022-12-22. It has since remained available on npm for 1306 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.12.1

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2022-11-30, unremoved on npm for 1328d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2022-11-30. It has since remained available on npm for 1328 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.12.0

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2022-11-18, unremoved on npm for 1340d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2022-11-18. It has since remained available on npm for 1340 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.11.1

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2022-09-30, unremoved on npm for 1389d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2022-09-30. It has since remained available on npm for 1389 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.11.0

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2022-09-28, unremoved on npm for 1391d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2022-09-28. 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.10.2

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2022-09-14, unremoved on npm for 1405d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2022-09-14. It has since remained available on npm for 1405 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.10.1

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2022-07-28, unremoved on npm for 1453d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2022-07-28. It has since remained available on npm for 1453 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.