@clickhouse/client
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.18.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.