← Home

@ledgerhq/coin-concordium

Concordium coin integration

27
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

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

Keywords

LedgerLedgerWalletconcordiumHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@ledgerhq/concordium-core AI (dependencies): @ledgerhq/concordium-core is a first-party LedgerHQ dependency consistent with this package's purpose; stable false positive for this package. ai
provenance no-provenance AI (provenance): LedgerHQ publishes via CI bot without Sigstore provenance; package is from the well-known ledger-live monorepo. Acceptable for this publisher. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding is used to parse CBOR-encoded memo fields from Concordium blockchain transactions — standard blockchain data handling, not malicious payload obfuscation. ai
phantom-deps phantom-dep:invariant AI (phantom-deps): invariant is declared as a runtime dependency in package.json; phantom-dep finding is a false positive for this package. ai

Versions (showing 27 of 27)

Version Deps Published
0.16.0 14 / 13
0.15.0 15 / 13
0.14.0 15 / 13
0.13.1 15 / 13
0.13.0 15 / 13
0.12.1 15 / 13
0.12.0 15 / 13
0.11.0 15 / 13
0.10.0 15 / 13
0.9.2 15 / 13
0.9.1 15 / 13
0.9.0 15 / 13
0.8.0 15 / 13
0.7.1 15 / 11
0.7.0 15 / 11
0.6.0 16 / 11
0.5.0 16 / 11
0.4.0 16 / 10
0.3.5 10 / 10
0.3.4 10 / 10
0.3.3 10 / 10
0.3.2 10 / 10
0.3.1 10 / 10
0.3.0 10 / 10
0.2.2 10 / 9
0.2.1 10 / 9
0.2.0 10 / 9

v0.16.0

1 finding
INFO No provenance attestation provenance

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

v0.15.0

1 finding
INFO No provenance attestation provenance

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

v0.14.0

1 finding
INFO No provenance attestation provenance

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