← Home

@ledgerhq/zcash-utils

npm Repository

Native Zcash key derivation and shielded sync — Node.js (NAPI)

8
Versions
MIT
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.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): NAPI-RS native bindings for multiple platforms; expected for this Rust/Node.js package. ai
semgrep semgrep:child-process-import AI (semgrep): Used only for musl detection via 'which ldd'; standard NAPI-RS runtime pattern. ai
semgrep semgrep:child-process-execsync AI (semgrep): execSync('which ldd') is a benign libc-type detection call, not arbitrary code execution. ai

Versions (showing 8 of 8)

Version Deps Published
0.3.1 0 / 5
0.3.0 0 / 5
0.2.0 0 / 5
0.1.5 0 / 5
0.1.4 0 / 5
0.1.2 0 / 5
0.1.1 0 / 5
0.1.0 0 / 5

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

2 findings
HIGH Bundled binary files (6) npm-metadata

Package contains compiled binaries that could be backdoors: • index.darwin-arm64.node • index.darwin-x64.node • index.linux-arm64-gnu.node • index.linux-x64-gnu.node • index.win32-arm64-msvc.node • index.win32-x64-msvc.node

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

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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