← Home

@ledgerhq/hw-app-algorand

71
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

LedgerLedgerWalletalgoAlgorandNanoSBlueHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Org-wide Ledger maintainer rotation, consistent across ledgerhq packages. ai
maintainer-change maintainer-removed AI (maintainer-change): Same rotation; old Ledger employees removed, not a takeover. ai
provenance publisher-changed-stale AI (provenance): Long-stable publisher change (1454d) inconsistent with compromise. ai
semgrep semgrep:hex-decode AI (semgrep): Buffer.from(message, 'hex') is standard hex decoding of transaction data for hardware wallet transport — expected and benign for this package. ai

Versions (showing 71 of 71)

Version Deps Published
6.35.6 6 / 10
6.35.5 6 / 10
6.35.4 6 / 10
6.35.3 6 / 10
6.35.2 6 / 10
6.35.1 6 / 10
6.35.0 6 / 10
6.34.1 6 / 10
6.34.0 6 / 10
6.33.0 6 / 10
6.32.0 6 / 10
6.31.12 6 / 9
6.31.11 6 / 9
6.31.10 6 / 9
6.31.9 6 / 9
6.31.8 6 / 9
6.31.7 6 / 9
6.31.6 6 / 9
6.31.5 6 / 9
6.31.4 6 / 9
6.31.3 6 / 9
6.31.2 6 / 10
6.31.1 6 / 10
6.31.0 6 / 10
6.30.0 6 / 10
6.29.4 6 / 9
6.29.3 6 / 9
6.29.2 6 / 9
6.29.1 6 / 9
6.29.0 6 / 9
6.28.6 6 / 9
6.28.5 6 / 9
6.28.4 6 / 9
6.28.3 6 / 9
6.28.2 6 / 9
6.28.1 6 / 9
6.28.0 6 / 9
6.27.20 6 / 9
6.27.19 6 / 9
6.27.18 6 / 9
6.27.17 6 / 9
6.27.16 6 / 9
6.27.15 6 / 9
6.27.14 6 / 9
6.27.13 6 / 10
6.27.12 6 / 1
6.27.11 6 / 1
6.27.10 6 / 1
6.27.9 6 / 1
6.27.8 6 / 1
6.27.7 6 / 1
6.27.6 6 / 1
6.27.5 6 / 1
6.27.4 6 / 1
6.27.3 6 / 1
6.27.2 6 / 1
6.27.1 6 / 0
6.24.1 6 / 0
6.24.0 6 / 0
6.20.0 6 / 0
6.19.0 6 / 0
6.11.2 6 / 0
6.11.0 6 / 0
6.10.0 6 / 0
6.7.0 3 / 0
6.3.0 3 / 0
6.2.0 3 / 0
6.1.0 3 / 0
6.0.2 3 / 0
6.0.1 3 / 0
6.0.0 3 / 0

v6.35.6

1 finding
LOW No provenance attestation provenance

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

v6.35.5

1 finding
LOW No provenance attestation provenance

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

v6.31.0

1 finding
LOW No provenance attestation provenance

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

v6.30.0

1 finding
LOW No provenance attestation provenance

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

v6.29.4

1 finding
LOW No provenance attestation provenance

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

v6.29.3

1 finding
LOW No provenance attestation provenance

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

v6.29.2

1 finding
LOW No provenance attestation provenance

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

v6.29.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.29.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.28.6

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

This 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.

LOW No provenance attestation provenance

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

v6.28.5

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

This 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.

LOW No provenance attestation provenance

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

v6.28.4

2 findings
MEDIUM Publisher changed: sergii-shkolin → 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 (sergii-shkolin) 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.28.3

2 findings
MEDIUM Publisher changed: sergii-shkolin → ldg-github-ci (on 2024-01-31, unremoved on npm for 902d) provenance

This 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.

LOW No provenance attestation provenance

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

v6.28.2

2 findings
MEDIUM Publisher changed: sergii-shkolin → ldg-github-ci (on 2024-01-23, unremoved on npm for 910d) provenance

This 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.

LOW No provenance attestation provenance

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

v6.28.1

1 finding
LOW No provenance attestation provenance

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

v6.28.0

1 finding
LOW No provenance attestation provenance

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

v6.27.20

1 finding
LOW No provenance attestation provenance

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

v6.27.19

1 finding
LOW No provenance attestation provenance

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

v6.27.18

1 finding
LOW No provenance attestation provenance

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

v6.27.17

1 finding
LOW No provenance attestation provenance

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

v6.27.16

1 finding
LOW No provenance attestation provenance

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

v6.27.15

1 finding
LOW No provenance attestation provenance

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

v6.27.14

1 finding
LOW No provenance attestation provenance

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

v6.27.13

1 finding
LOW No provenance attestation provenance

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

v6.27.12

1 finding
LOW No provenance attestation provenance

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

v6.27.11

1 finding
LOW No provenance attestation provenance

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

v6.27.10

1 finding
LOW No provenance attestation provenance

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

v6.27.9

1 finding
LOW No provenance attestation provenance

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

v6.27.8

1 finding
LOW No provenance attestation provenance

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

v6.27.7

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.27.6

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

This 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 1390 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.27.5

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

This 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 1392 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.27.4

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

This 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 1406 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.27.3

2 findings
MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2022-08-31, unremoved on npm for 1420d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-08-31. It has since remained available on npm for 1420 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.27.2

2 findings
MEDIUM Publisher changed: gre → sergii-shkolin (on 2022-07-28, unremoved on npm for 1454d) 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 1454 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.27.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gre → juan-cortes (on 2022-04-13, known maintainer) provenance

This version was published by a different npm account (juan-cortes) than the most recent previously approved version (gre) on 2022-04-13, but juan-cortes is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v6.24.1

1 finding
LOW No provenance attestation provenance

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

v6.24.0

1 finding
LOW No provenance attestation provenance

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

v6.20.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.0

1 finding
LOW No provenance attestation provenance

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

v6.11.2

1 finding
LOW No provenance attestation provenance

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

v6.11.0

1 finding
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.7.0

1 finding
LOW No provenance attestation provenance

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

v6.3.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.1.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. Consider requesting the maintainer enable provenance via CI/CD.

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.