← Home

@uwdata/mosaic-duckdb

npm Repository Homepage

A Promise-based DuckDB API and Node.js data server.

13
Versions
BSD-3-Clause
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

jheerluke-s-snyderdomoritz

Keywords

duckdbservernodearrowmosaic

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): domoritz (Dominik Moritz) is a known UW IDL collaborator on the Mosaic project; legitimate maintainer addition. ai
dependencies unvetted-dep:@duckdb/node-api AI (dependencies): Official DuckDB Node.js API package; legitimate replacement for the duckdb dep. ai
dependencies unvetted-dep:@uwdata/mosaic-sql AI (dependencies): Sibling package in the same uwdata/mosaic monorepo; stable false positive. ai

Versions (showing 13 of 13)

Version Deps Published
0.25.0 3 / 2
0.24.3 3 / 2
0.23.0 3 / 2
0.22.0 3 / 0
0.21.1 3 / 0
0.21.0 3 / 0
0.20.1 3 / 0
0.20.0 3 / 0
0.19.0 3 / 0
0.18.0 3 / 0
0.17.0 3 / 0
0.16.2 3 / 0
0.16.1 3 / 0

v0.25.0

2 findings
HIGH Publisher changed: jheer → domoritz (on 2026-05-02) provenance

This version was published by a different npm account than previous versions on 2026-05-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.23.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.22.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.21.1

1 finding
LOW No provenance attestation provenance

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

v0.21.0

1 finding
LOW No provenance attestation provenance

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

v0.20.1

1 finding
LOW No provenance attestation provenance

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

v0.20.0

1 finding
LOW No provenance attestation provenance

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

v0.19.0

1 finding
LOW No provenance attestation provenance

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

v0.18.0

1 finding
LOW No provenance attestation provenance

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

v0.17.0

1 finding
LOW No provenance attestation provenance

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

v0.16.2

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

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.