← Home

@ledgerhq/coin-algorand

npm Repository Homepage

Ledger Algorand Coin integration

22
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

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

Keywords

LedgerLedgerWalletalgoAlgorandHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:algo-msgpack-with-bigint AI (dependencies): algo-msgpack-with-bigint is a legitimate Algorand ecosystem dependency (msgpack with BigInt support for algosdk). Expected for an Algorand coin integration package. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding in this package is standard cryptographic signature handling for Algorand transaction broadcasting — not malicious payload obfuscation. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decode appears only in test mocks (jest.fn); entirely benign test infrastructure for a blockchain coin library. ai

Versions (showing 22 of 22)

Version Deps Published
1.6.2 17 / 10
1.6.1 17 / 10
1.6.0 17 / 10
1.5.3 17 / 10
1.5.2 17 / 10
1.5.1 17 / 10
1.5.0 17 / 10
1.4.0 17 / 10
1.3.1 17 / 8
1.3.0 17 / 8
1.2.0 16 / 8
1.1.0 16 / 8
1.0.0 16 / 7
0.17.2 17 / 7
0.17.1 17 / 7
0.17.0 17 / 7
0.15.2 17 / 6
0.15.1 17 / 6
0.15.0 17 / 6
0.14.0 17 / 6
0.13.0 17 / 6
0.12.0 17 / 6

v1.6.2

1 finding
LOW No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.3

1 finding
LOW No provenance attestation provenance

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

v1.5.2

1 finding
LOW No provenance attestation provenance

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

v1.5.1

1 finding
LOW No provenance attestation provenance

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

v1.5.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.

v1.4.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.

v1.3.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.

v1.3.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.

v1.2.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.

v1.1.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.