@ledgerhq/concordium-core
3
Versions
—
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): This is a Concordium blockchain serialization library; hex encoding/decoding of credential IDs, keys, and binary protocol data is expected and routine. Not a malicious payload indicator. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode appears only in test files exercising CBOR memo decoding. Entirely benign test code for this cryptographic utility library. | ai | |
| provenance | no-provenance | AI (provenance): Published by official LedgerHQ CI publisher from the ledger-live monorepo; lack of Sigstore provenance is acceptable given the established publisher identity. | ai |
v0.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.
v0.3.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.