← Home

@databricks/sql

npm Repository Homepage
14
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Keywords

databricks sqlhiveserver2apachehivehs2clientthriftnodejsjshivehive js

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:patch-package AI (phantom-deps): patch-package is config-referenced, not imported; expected. ai
install-scripts install-script:postinstall AI (install-scripts): postinstall is patch-package, standard local dependency patching; stable for this package. ai
semgrep semgrep:child-process-import AI (semgrep): Used solely for musl detection in native binary loader; stable pattern for this package. ai
semgrep semgrep:child-process-execsync AI (semgrep): execSync('which ldd') is a musl/glibc detection heuristic for napi-rs native module routing; not malicious. ai
provenance publisher-changed AI (provenance): Transition from individual to GitHub Actions CI/CD publish is expected for a Databricks org package. ai
provenance missing-githead AI (provenance): gitHead absence is a side-effect of the CI/CD publish migration; stable for this package. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped official Databricks package; Levenshtein match to 'qs' is purely coincidental and not a typosquat. ai
phantom-deps phantom-dep:commander AI (phantom-deps): commander is listed as a runtime dependency; phantom-dep heuristic misfires here. ai

Versions (showing 14 of 14)

Version Deps Published
2.0.0 11 / 26
1.17.0 11 / 28
1.16.0 11 / 28
1.15.0 10 / 28
1.14.0 10 / 28
1.13.0 11 / 28
1.12.0 11 / 28
1.11.0 11 / 28
1.10.0 11 / 28
1.9.0 11 / 28
1.3.0 9 / 20
1.1.1 6 / 20
1.1.0 6 / 20
1.0.0 5 / 20

v2.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v1.17.0

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v1.3.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: patch-package

LOW No provenance attestation provenance

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

v1.1.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: patch-package

LOW No provenance attestation provenance

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

v1.1.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: patch-package

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.

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