← Home

@deephaven-enterprise/query-utils

npm

Deephaven Enterprise Query Utils

8
Versions
SEE LICENSE IN LICENSE.md
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

vbabichbinglesmikebenderdeephaven-botmattrunyon

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): High-volume Deephaven enterprise package with 238 versions; gap reflects release cadence, not takeover. ai
dependencies unvetted-dep:@deephaven/log AI (dependencies): First-party Deephaven org dependency; stable pattern across all versions of this monorepo package. ai
dependencies unvetted-dep:@deephaven/utils AI (dependencies): First-party Deephaven org dependency; stable pattern across all versions of this monorepo package. ai
dependencies unvetted-dep:@deephaven/jsapi-types AI (dependencies): First-party Deephaven org dependency; stable pattern across all versions of this monorepo package. ai
dependencies unvetted-dep:@deephaven-enterprise/jsapi-types AI (dependencies): Same-org sibling dep via file: path; standard monorepo pattern for this package. ai
npm-metadata url-dep:@deephaven-enterprise/jsapi-types AI (npm-metadata): file: dep is a monorepo sibling; consistent pattern across 238 published versions. ai

Versions (showing 8 of 8)

Version Deps Published
2026.1.37 6 / 0
2026.1.36 6 / 0
2026.1.35 6 / 0
2026.1.34 6 / 0
2026.1.33 6 / 0
2026.1.32 6 / 0
2026.1.31 6 / 0
2026.1.30 6 / 0

v2026.1.37

1 finding
LOW No provenance attestation provenance

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

v2026.1.36

1 finding
LOW No provenance attestation provenance

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

v2026.1.35

1 finding
LOW No provenance attestation provenance

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

v2026.1.34

1 finding
LOW No provenance attestation provenance

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

v2026.1.33

1 finding
LOW No provenance attestation provenance

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

v2026.1.32

1 finding
LOW No provenance attestation provenance

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

v2026.1.31

1 finding
LOW No provenance attestation provenance

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

v2026.1.30

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.