← Home

@quicknode/sdk

npm Repository Homepage

A SDK from [QuickNode](https://www.quicknode.com/) making it easy for developers to interact with QuickNode's services.

9
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

0xsergenalopezquiknodebartekwitczakalejandrofabiancamposferhatqnqnzachjmitschsahilsenjosescasanovavittitowmarkwu35mikehale-qngayleqnmaurodelazerielopezqnjustinquickestnoderaquicknodemikemaccanaaaeqnshayaanakbarquiknodedavevrohlfsrorygraman-qnsandeeppainulylucqnechung.quiknode.iosamueljuddronyqnqn-srikanthmcastilla

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation is a legitimate supply chain improvement for this package. ai
npm-metadata bundled-binaries AI (npm-metadata): napi-rs native addon; .node binaries are the intended distribution mechanism for this package. ai
semgrep semgrep:child-process-execsync AI (semgrep): execSync('ldd --version') is standard napi-rs musl detection boilerplate, not arbitrary command execution. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used solely for ldd musl detection in napi-rs loader; stable false positive for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): NAPI_RS_NATIVE_LIBRARY_PATH override is standard napi-rs escape hatch for custom binary paths. ai

Versions (showing 9 of 9)

Version Deps Published
3.5.0 0 / 3
3.1.1 0 / 3
3.1.0 0 / 3
2.6.0 5 / 10
2.5.2 5 / 10
2.4.2 5 / 10
2.4.1 5 / 10
2.4.0 5 / 10
2.3.0 5 / 10

v2.4.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jmitsch → josescasanova (on 2025-03-28, known maintainer) provenance

This version was published by a different npm account (josescasanova) than the most recent previously approved version (jmitsch) on 2025-03-28, but josescasanova is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.4.1

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

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