← Home

@ledgerhq/live-signer-concordium

npm Repository Homepage

Ledger Hardware Wallet Concordium Signer

8
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

LedgerLedgerWalletCCDConcordiumHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@ledgerhq/errors AI (dependencies): First-party LedgerHQ package from the same ledger-live monorepo; expected internal dependency, not a third-party risk. ai
dependencies unvetted-dep:@ledgerhq/coin-concordium AI (dependencies): First-party LedgerHQ package from the same ledger-live monorepo; expected internal dependency, not a third-party risk. ai
dependencies unvetted-dep:@ledgerhq/concordium-core AI (dependencies): First-party LedgerHQ package from the same ledger-live monorepo; expected internal dependency, not a third-party risk. ai

Versions (showing 8 of 8)

Version Deps Published
0.4.0 7 / 7
0.3.3 7 / 7
0.3.2 7 / 7
0.3.1 7 / 7
0.3.0 7 / 7
0.2.2 6 / 7
0.2.1 6 / 7
0.2.0 6 / 7

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

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