Skip to content
QuenchWorks

timescaledb

Chart · Time series · standard · v0.0.14

digest pinnedcosign signedSPDX SBOMSLSA provenanceamd64 · arm64Rebuilt 2026-09-06

PostgreSQL 17 plus the open TimescaleDB extension (Apache-only edition), adding hypertables, continuous aggregates, and time-series functions for high-ingest metrics and event data. Built clean-licensed from source on Wolfi (no TSL community code).

Version

The latest line lives at the base page; older lines have their own page so you can pin and verify exactly that version. Only the most recent releases are listed — an older chart pins an older image digest.

Deployed image digest

sha256:6d786c1c6306b185ef8e1aef144201c3c27a4ee42c17bfe1caa5ed3913e2aac2

Chart OCI version

oci://ghcr.io/quenchworks/charts/timescaledb:0.0.14

The chart pins its image by this signed digest, so you never track it yourself. Signatures, SBOM, and provenance attach to the same digest.

Signed
cosign keyless
SBOM
SPDX, on image
Provenance
SLSA build
Architectures
amd64, arm64
Runs as
nonroot (uid 1001)
Root filesystem
read-only
Image size
148.6 MB

Security report (Trivy)

C· 55/1005 fixable · rebuild clears them

Vulnerability detail

timescaledb 2.29.2 · 5 CVE
CVESeverityPackageInstalledFixed inTitle
CVE-2026-18374MEDIUMglibc-2.442.44-r52.44-r6glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string
CVE-2026-18374MEDIUMglibc-2.44-locale-posix2.44-r52.44-r6glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string
CVE-2026-18374MEDIUMld-linux-2.442.44-r52.44-r6glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string
CVE-2026-18374MEDIUMlibcrypt1-2.442.44-r52.44-r6glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string
CVE-2026-85091MEDIUMzlib1.3.2-r51.3.3-r0zlib versions 1.3.1.2 through 1.3.2 contain a heap buffer overflow vul ...
0
Critical
0
High
5
Medium
0
Low
0
Unknown

Security report (Trivy) · image timescaledb 2.29.2

Install the chart

Deploy to Kubernetes with hardened defaults. The chart pins its image by signed digest, so you never track it yourself.

Install (latest)

helm install my-timescaledb oci://ghcr.io/quenchworks/charts/timescaledb --version 0.0.14

Deploys image (digest-pinned)

ghcr.io/quenchworks/images/timescaledb@sha256:6d786c1c6306b185ef8e1aef144201c3c27a4ee42c17bfe1caa5ed3913e2aac2
ghcr.io/quenchworks/images/postgres-exporter@sha256:fab4d5790531b5cd9daad06a8651fe4ca1009620701394b81c34ed9b7ebc9bbb
Chart version
0.0.14
App version
2.29.2
Chart license
Apache-2.0
App license
Apache-2.0
Service port
5432
Signed
cosign (keyless)
Values schema
yes
Last published
2026-08-31

Verify the chart

cosign verify ghcr.io/quenchworks/charts/timescaledb:0.0.14 \
  --certificate-identity-regexp 'https://github.com/quenchworks/.+' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

Transparency

The chart publishes its attestations on GitHub and the image it deploys carries its own on the same digest, publicly verifiable with the commands above. Both log to the Sigstore transparency log (Rekor), which cosign verify checks for you.

Upstream project: https://www.timescale.com