← Home

@clickhouse/client

npm Repository Homepage
34
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mikhail.shustov-clickhousemichael.anastasakis4b819b88c84bsantranciscohoorayimhelpingtreslechesvineethasok

Keywords

clickhousesqlclient

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff source-size-tripled AI (source-diff): Size increase explained by removal of @clickhouse/client-common dep and inlining its code; not injected payload. ai
source-diff large-new-source-files AI (source-diff): 112 new files consistent with merging client-common into this package; SLSA provenance confirms CI/CD origin. ai
publish-pattern rapid-publish AI (publish-pattern): Automated GitHub Actions release pipeline; rapid publish is expected behavior for this package. ai
maintainer-change maintainer-removed AI (maintainer-change): Package published via GitHub Actions CI/CD with SLSA provenance; maintainer list change reflects org automation, not takeover. ai
dependencies unvetted-dep:@clickhouse/client-common AI (dependencies): This is a sibling package in the same ClickHouse JS client monorepo, published together under the same SLSA-attested CI/CD pipeline. Not a third-party risk. ai

Versions (showing 34 of 34)

Version Deps Published
1.23.1 0 / 1
1.23.0 0 / 1
1.22.0 1 / 1
1.21.0 1 / 1
1.20.0 1 / 1
1.19.0 1 / 1
1.18.5 1 / 1
1.18.4 1 / 1
1.18.3 1 / 1
1.14.0 1 / 1
1.13.0 1 / 0
1.12.1 1 / 0
1.12.0 1 / 0
1.11.2 1 / 0
1.11.1 1 / 0
1.11.0 1 / 0
1.10.1 1 / 0
1.10.0 1 / 0
1.9.1 1 / 0
1.9.0 1 / 0
1.8.1 1 / 0
1.8.0 1 / 0
1.7.0 1 / 0
1.6.0 1 / 0
1.5.0 1 / 0
1.4.1 1 / 0
1.4.0 1 / 0
1.3.0 1 / 0
1.2.0 1 / 0
1.1.0 1 / 0
1.0.2 1 / 0
1.0.1 1 / 0
1.0.0 1 / 0
0.100.1 1 / 1

v1.23.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.23.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.11.1

1 finding
LOW No provenance attestation provenance

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

v1.11.0

1 finding
LOW No provenance attestation provenance

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

v1.10.1

1 finding
LOW No provenance attestation provenance

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

v1.10.0

1 finding
LOW No provenance attestation provenance

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

v1.9.1

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
LOW No provenance attestation provenance

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

v1.8.1

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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.