← Home

@duckviz/db

In-browser SQL data engine powered by DuckDB-WASM. File ingestion, query execution, IndexedDB persistence, and log parsing — all client-side.

10
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

vikas-cldcvr

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:xlsx AI (phantom-deps): Bundled library; may be consumed indirectly via build output rather than direct ESM import. ai
phantom-deps phantom-dep:papaparse AI (phantom-deps): Bundled library; may be consumed indirectly via build output rather than direct ESM import. ai
phantom-deps phantom-dep:fast-xml-parser AI (phantom-deps): Bundled library; may be consumed indirectly via build output rather than direct ESM import. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @duckviz/db is a DuckDB-WASM engine, not a typosquat of pg; Levenshtein match is coincidental. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @duckviz/db is a DuckDB-WASM engine, not a typosquat of qs; Levenshtein match is coincidental. ai

Versions (showing 10 of 10)

Version Deps Published
0.7.0 0 / 14
0.6.1 0 / 13
0.5.2 0 / 13
0.5.0 0 / 13
0.4.0 0 / 13
0.3.1 0 / 13
0.2.5 4 / 9
0.2.4 4 / 9
0.2.3 4 / 9
0.1.0 4 / 8

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

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