timescaledb-oss
TimescaleDB (Apache 2.0 Edition)
TimescaleDB is an open-source time-series database built on PostgreSQL. It enables fast analytics, efficient storage, and powerful querying for time-series workloads.
Note
This image contains only the Apache 2.0 licensed components of TimescaleDB (known as "TimescaleDB Apache-2 Edition") to ensure CNCF licensing compliance. Advanced features requiring the Timescale License (TSL) are not included.
This image provides a convenient way to deploy and manage the open-source core of TimescaleDB with CloudNativePG.
Usage
1. Add the TimescaleDB extension image to your Cluster
Define the timescaledb-oss extension under the postgresql.extensions section
of your Cluster resource. For example:
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
name: cluster-timescaledb
spec:
imageName: ghcr.io/cloudnative-pg/postgresql:18-minimal-trixie
instances: 1
storage:
size: 1Gi
postgresql:
shared_preload_libraries:
- “timescaledb”
parameters:
timescaledb.telemetry_level: ‘off’
max_locks_per_transaction: ‘128’
extensions:
- name: timescaledb-oss
image:
# renovate: suite=trixie-pgdg depName=postgresql-18-timescaledb
reference: ghcr.io/cloudnative-pg/timescaledb-oss:2.32.0-18-trixie
2. Enable the extension in a database
You can install timescaledb in a specific database by creating or updating a
Database resource. For example, to enable it in the app database:
apiVersion: postgresql.cnpg.io/v1
kind: Database
metadata:
name: cluster-timescaledb-app
spec:
name: app
owner: app
cluster:
name: cluster-timescaledb
extensions:
- name: timescaledb
# renovate: suite=trixie-pgdg depName=postgresql-18-timescaledb extractVersion=^(?<version>\d+\.\d+\.\d+)
version: '2.32.0'
3. Verify installation
Once the database is ready, connect to it with psql and run:
\dx
You should see timescaledb listed among the installed extensions.
4. Create a hypertable
To use TimescaleDB's time-series features, create a hypertable:
-- Create a regular table
CREATE TABLE sensor_data (
time TIMESTAMPTZ NOT NULL,
sensor_id INTEGER,
temperature DOUBLE PRECISION,
humidity DOUBLE PRECISION
);
– Convert it to a hypertable
SELECT create_hypertable(‘sensor_data’, ’time’);
– Insert some data
INSERT INTO sensor_data VALUES (NOW(), 1, 21.5, 45.0);
Maintainers
This container image is maintained by @shuusan.
License
This image contains only the Apache 2.0 licensed components of TimescaleDB. Features requiring the Timescale License (TSL) are not included to ensure compliance with CNCF licensing requirements.
All relevant license and copyright information for the timescaledb-oss extension
and its dependencies are bundled within the image at:
/licenses/
By using this image, you agree to comply with the terms of the licenses contained therein.
For further information, refer to Software Licensing: Timescale License (TSL).
Overview
TimescaleDB is an open-source time-series database built on PostgreSQL. It enables fast analytics, efficient storage, and powerful querying for time-series workloads.
Package details
- Extension version
- 2.32.0
- Image built
- Publisher
- cloudnative-pg
- Build
- Debian
- Platform
- PG 18 · Trixie · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/timescaledb
- Upstream homepage ↗github.com/timescale/timescaledb
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION timescaledb;- SQL version
2.32.0
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'timescaledb' |
These recipe settings are used in automated smoke tests.
OpenSSF scorecard
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.
View information about checks. Automated results are informational only; some categories may not apply to this project.
Scanned · View OpenSSF report ↗
Dangerous-Workflow0
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: dangerous workflow patterns detected
- Warn: untrusted code checkout '${{ github.event.pull_request.head.sha }}': .github/workflows/release_changelog.yml:55
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-Protection3
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection is not maximal on development and all release branches
- Info: 'allow deletion' disabled on branch 'main'
- Info: 'allow deletion' disabled on branch '2.30.x'
- Info: 'allow deletion' disabled on branch '2.26.x'
- Info: 'allow deletion' disabled on branch '2.25.x'
- Info: 'allow deletion' disabled on branch '2.24.x'
- Info: 'allow deletion' disabled on branch '2.23.x'
- Info: 'allow deletion' disabled on branch '2.22.x'
- Info: 'allow deletion' disabled on branch '2.21.x'
- Info: 'force pushes' disabled on branch 'main'
- Info: 'force pushes' disabled on branch '2.30.x'
- Info: 'force pushes' disabled on branch '2.26.x'
- Info: 'force pushes' disabled on branch '2.25.x'
- Info: 'force pushes' disabled on branch '2.24.x'
- Info: 'force pushes' disabled on branch '2.23.x'
- Info: 'force pushes' disabled on branch '2.22.x'
- Info: 'force pushes' disabled on branch '2.21.x'
- Warn: required approving review count is 1 on branch 'main'
- Warn: branch '2.30.x' does not require approvers
- Warn: branch '2.26.x' does not require approvers
- Warn: branch '2.25.x' does not require approvers
- Warn: branch '2.24.x' does not require approvers
- Warn: branch '2.23.x' does not require approvers
- Warn: branch '2.22.x' does not require approvers
- Warn: branch '2.21.x' does not require approvers
- Warn: codeowners review is required - but no codeowners file found in repo
- Warn: codeowners review is not required on branch '2.30.x'
- Warn: codeowners review is not required on branch '2.26.x'
- Warn: codeowners review is not required on branch '2.25.x'
- Warn: codeowners review is not required on branch '2.24.x'
- Warn: codeowners review is not required on branch '2.23.x'
- Warn: codeowners review is not required on branch '2.22.x'
- Warn: codeowners review is not required on branch '2.21.x'
- Info: status check found to merge onto on branch 'main'
- Info: status check found to merge onto on branch '2.30.x'
- Info: status check found to merge onto on branch '2.26.x'
- Info: status check found to merge onto on branch '2.25.x'
- Info: status check found to merge onto on branch '2.24.x'
- Info: status check found to merge onto on branch '2.23.x'
- Info: status check found to merge onto on branch '2.22.x'
- Info: status check found to merge onto on branch '2.21.x'
- Info: PRs are required in order to make changes on branch 'main'
Code-Review10
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: all changesets reviewed
Maintained10
Determines if the project is "actively maintained".
Reasoning: 30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/llm-fuzzer.yaml:80
- Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/llm-fuzzer.yaml:81
- Info: jobLevel 'issues' permission set to 'read': .github/workflows/llm-fuzzer.yaml:82
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/release_sanity.yml:240
- Info: jobLevel 'issues' permission set to 'read': .github/workflows/release_sanity.yml:28
- Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/release_sanity.yml:29
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/release_sanity.yml:27
- Warn: no topLevel permission defined: .github/workflows/abi.yaml:1
- Warn: no topLevel permission defined: .github/workflows/apt-installcheck.yaml:1
- Warn: no topLevel permission defined: .github/workflows/apt-packages.yaml:1
- Warn: no topLevel permission defined: .github/workflows/backport-trigger.yaml:1
- Warn: topLevel 'statuses' permission set to 'write': .github/workflows/backport.yaml:24
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/backport.yaml:20
- Warn: topLevel 'actions' permission set to 'write': .github/workflows/backport.yaml:23
- Info: topLevel 'contents' permission set to 'read': .github/workflows/build-deb-artifacts.yaml:20
- Warn: no topLevel permission defined: .github/workflows/catalog-updates-check.yaml:1
- Warn: no topLevel permission defined: .github/workflows/changelog-check.yaml:1
- Warn: no topLevel permission defined: .github/workflows/coccinelle.yaml:1
- Warn: no topLevel permission defined: .github/workflows/code_style.yaml:1
- Warn: no topLevel permission defined: .github/workflows/docker-images.yaml:1
- Warn: no topLevel permission defined: .github/workflows/extras-diagnostic.yaml:1
- Warn: no topLevel permission defined: .github/workflows/homebrew.yaml:1
- Warn: no topLevel permission defined: .github/workflows/issue-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/label-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/label-released-prs.yaml:1
- Warn: no topLevel permission defined: .github/workflows/libfuzzer.yaml:1
- Warn: no topLevel permission defined: .github/workflows/linux-32bit-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/linux-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/llm-fuzzer.yaml:1
- Warn: no topLevel permission defined: .github/workflows/loader_check.yml:1
- Warn: no topLevel permission defined: .github/workflows/memory-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/nightly_cloud_smoke_test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pg_ladybug.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pg_upgrade-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pgspot.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-approvals.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-validation.yaml:1
- Warn: no topLevel permission defined: .github/workflows/prerelease-sanity.yaml:1
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release_changelog.yml:14
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/release_feature_freeze_ceremony.yaml:26
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/release_post_release_ceremony.yaml:17
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release_release.yml:22
- Warn: no topLevel permission defined: .github/workflows/release_sanity.yml:1
- Warn: no topLevel permission defined: .github/workflows/rpm-packages.yaml:1
- Warn: no topLevel permission defined: .github/workflows/sanitizer-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/shellcheck.yaml:1
- Warn: no topLevel permission defined: .github/workflows/snapshot-abi.yaml:1
- Warn: no topLevel permission defined: .github/workflows/sqlsmith.yaml:1
- Warn: no topLevel permission defined: .github/workflows/stalebot.yaml:1
- Warn: no topLevel permission defined: .github/workflows/tests-fail-on-old-code.yaml:1
- Warn: no topLevel permission defined: .github/workflows/trigger-package-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/trigger-prerelease-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/update-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/windows-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/windows-packages.yaml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies6
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 6
- Info: Possibly incomplete results: error parsing shell code: invalid parameter name: .github/workflows/libfuzzer.yaml:198
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:88
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:94
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:103
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:113
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:119
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:130
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:142
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:150
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:164
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:210
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:216
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:227
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:252
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:256
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:261
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:272
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:279
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:309
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:359
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:377
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:405
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:419
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_release.yml:81: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_release.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:196: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:204: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:212: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:220: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:180: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:188: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: pipCommand not pinned by hash: .github/workflows/backport.yaml:34
- Warn: pipCommand not pinned by hash: .github/workflows/catalog-updates-check.yaml:19
- Warn: pipCommand not pinned by hash: .github/workflows/changelog-check.yaml:32
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:93
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:53
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:16
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:244
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:245
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:250
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:252
- Warn: pipCommand not pinned by hash: .github/workflows/label-released-prs.yaml:28
- Warn: npmCommand not pinned by hash: .github/workflows/llm-fuzzer.yaml:208
- Warn: pipCommand not pinned by hash: .github/workflows/pg_upgrade-test.yaml:77
- Warn: pipCommand not pinned by hash: .github/workflows/pgspot.yaml:52
- Warn: pipCommand not pinned by hash: .github/workflows/release_feature_freeze_ceremony.yaml:103
- Info: 155 out of 155 GitHub-owned GitHubAction dependencies pinned
- Info: 18 out of 25 third-party GitHubAction dependencies pinned
- Info: 0 out of 14 pipCommand dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: SAST tool is not run on all commits -- score normalized to 0
- Warn: 0 commits out of 30 are checked with a SAST tool
Security-Policy10
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: SECURITY.md:1
- Info: Found linked content: SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
CII-Best-Practices5
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning: badge detected: Passing
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
TimescaleDB is an open-source time-series database built on PostgreSQL. It enables fast analytics, efficient storage, and powerful querying for time-series workloads.
Package details
- Extension version
- 2.32.0
- Image built
- Publisher
- cloudnative-pg
- Build
- Debian
- Platform
- PG 18 · Trixie · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/timescaledb
- Upstream homepage ↗github.com/timescale/timescaledb
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION timescaledb;- SQL version
2.32.0
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'timescaledb' |
These recipe settings are used in automated smoke tests.
OpenSSF scorecard
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.
View information about checks. Automated results are informational only; some categories may not apply to this project.
Scanned · View OpenSSF report ↗
Dangerous-Workflow0
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: dangerous workflow patterns detected
- Warn: untrusted code checkout '${{ github.event.pull_request.head.sha }}': .github/workflows/release_changelog.yml:55
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-Protection3
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection is not maximal on development and all release branches
- Info: 'allow deletion' disabled on branch 'main'
- Info: 'allow deletion' disabled on branch '2.30.x'
- Info: 'allow deletion' disabled on branch '2.26.x'
- Info: 'allow deletion' disabled on branch '2.25.x'
- Info: 'allow deletion' disabled on branch '2.24.x'
- Info: 'allow deletion' disabled on branch '2.23.x'
- Info: 'allow deletion' disabled on branch '2.22.x'
- Info: 'allow deletion' disabled on branch '2.21.x'
- Info: 'force pushes' disabled on branch 'main'
- Info: 'force pushes' disabled on branch '2.30.x'
- Info: 'force pushes' disabled on branch '2.26.x'
- Info: 'force pushes' disabled on branch '2.25.x'
- Info: 'force pushes' disabled on branch '2.24.x'
- Info: 'force pushes' disabled on branch '2.23.x'
- Info: 'force pushes' disabled on branch '2.22.x'
- Info: 'force pushes' disabled on branch '2.21.x'
- Warn: required approving review count is 1 on branch 'main'
- Warn: branch '2.30.x' does not require approvers
- Warn: branch '2.26.x' does not require approvers
- Warn: branch '2.25.x' does not require approvers
- Warn: branch '2.24.x' does not require approvers
- Warn: branch '2.23.x' does not require approvers
- Warn: branch '2.22.x' does not require approvers
- Warn: branch '2.21.x' does not require approvers
- Warn: codeowners review is required - but no codeowners file found in repo
- Warn: codeowners review is not required on branch '2.30.x'
- Warn: codeowners review is not required on branch '2.26.x'
- Warn: codeowners review is not required on branch '2.25.x'
- Warn: codeowners review is not required on branch '2.24.x'
- Warn: codeowners review is not required on branch '2.23.x'
- Warn: codeowners review is not required on branch '2.22.x'
- Warn: codeowners review is not required on branch '2.21.x'
- Info: status check found to merge onto on branch 'main'
- Info: status check found to merge onto on branch '2.30.x'
- Info: status check found to merge onto on branch '2.26.x'
- Info: status check found to merge onto on branch '2.25.x'
- Info: status check found to merge onto on branch '2.24.x'
- Info: status check found to merge onto on branch '2.23.x'
- Info: status check found to merge onto on branch '2.22.x'
- Info: status check found to merge onto on branch '2.21.x'
- Info: PRs are required in order to make changes on branch 'main'
Code-Review10
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: all changesets reviewed
Maintained10
Determines if the project is "actively maintained".
Reasoning: 30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/llm-fuzzer.yaml:80
- Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/llm-fuzzer.yaml:81
- Info: jobLevel 'issues' permission set to 'read': .github/workflows/llm-fuzzer.yaml:82
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/release_sanity.yml:240
- Info: jobLevel 'issues' permission set to 'read': .github/workflows/release_sanity.yml:28
- Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/release_sanity.yml:29
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/release_sanity.yml:27
- Warn: no topLevel permission defined: .github/workflows/abi.yaml:1
- Warn: no topLevel permission defined: .github/workflows/apt-installcheck.yaml:1
- Warn: no topLevel permission defined: .github/workflows/apt-packages.yaml:1
- Warn: no topLevel permission defined: .github/workflows/backport-trigger.yaml:1
- Warn: topLevel 'statuses' permission set to 'write': .github/workflows/backport.yaml:24
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/backport.yaml:20
- Warn: topLevel 'actions' permission set to 'write': .github/workflows/backport.yaml:23
- Info: topLevel 'contents' permission set to 'read': .github/workflows/build-deb-artifacts.yaml:20
- Warn: no topLevel permission defined: .github/workflows/catalog-updates-check.yaml:1
- Warn: no topLevel permission defined: .github/workflows/changelog-check.yaml:1
- Warn: no topLevel permission defined: .github/workflows/coccinelle.yaml:1
- Warn: no topLevel permission defined: .github/workflows/code_style.yaml:1
- Warn: no topLevel permission defined: .github/workflows/docker-images.yaml:1
- Warn: no topLevel permission defined: .github/workflows/extras-diagnostic.yaml:1
- Warn: no topLevel permission defined: .github/workflows/homebrew.yaml:1
- Warn: no topLevel permission defined: .github/workflows/issue-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/label-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/label-released-prs.yaml:1
- Warn: no topLevel permission defined: .github/workflows/libfuzzer.yaml:1
- Warn: no topLevel permission defined: .github/workflows/linux-32bit-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/linux-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/llm-fuzzer.yaml:1
- Warn: no topLevel permission defined: .github/workflows/loader_check.yml:1
- Warn: no topLevel permission defined: .github/workflows/memory-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/nightly_cloud_smoke_test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pg_ladybug.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pg_upgrade-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pgspot.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-approvals.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-validation.yaml:1
- Warn: no topLevel permission defined: .github/workflows/prerelease-sanity.yaml:1
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release_changelog.yml:14
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/release_feature_freeze_ceremony.yaml:26
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/release_post_release_ceremony.yaml:17
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release_release.yml:22
- Warn: no topLevel permission defined: .github/workflows/release_sanity.yml:1
- Warn: no topLevel permission defined: .github/workflows/rpm-packages.yaml:1
- Warn: no topLevel permission defined: .github/workflows/sanitizer-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/shellcheck.yaml:1
- Warn: no topLevel permission defined: .github/workflows/snapshot-abi.yaml:1
- Warn: no topLevel permission defined: .github/workflows/sqlsmith.yaml:1
- Warn: no topLevel permission defined: .github/workflows/stalebot.yaml:1
- Warn: no topLevel permission defined: .github/workflows/tests-fail-on-old-code.yaml:1
- Warn: no topLevel permission defined: .github/workflows/trigger-package-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/trigger-prerelease-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/update-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/windows-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/windows-packages.yaml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies6
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 6
- Info: Possibly incomplete results: error parsing shell code: invalid parameter name: .github/workflows/libfuzzer.yaml:198
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:88
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:94
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:103
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:113
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:119
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:130
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:142
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:150
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:164
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:210
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:216
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:227
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:252
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:256
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:261
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:272
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:279
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:309
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:359
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:377
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:405
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:419
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_release.yml:81: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_release.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:196: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:204: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:212: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:220: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:180: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:188: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: pipCommand not pinned by hash: .github/workflows/backport.yaml:34
- Warn: pipCommand not pinned by hash: .github/workflows/catalog-updates-check.yaml:19
- Warn: pipCommand not pinned by hash: .github/workflows/changelog-check.yaml:32
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:93
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:53
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:16
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:244
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:245
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:250
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:252
- Warn: pipCommand not pinned by hash: .github/workflows/label-released-prs.yaml:28
- Warn: npmCommand not pinned by hash: .github/workflows/llm-fuzzer.yaml:208
- Warn: pipCommand not pinned by hash: .github/workflows/pg_upgrade-test.yaml:77
- Warn: pipCommand not pinned by hash: .github/workflows/pgspot.yaml:52
- Warn: pipCommand not pinned by hash: .github/workflows/release_feature_freeze_ceremony.yaml:103
- Info: 155 out of 155 GitHub-owned GitHubAction dependencies pinned
- Info: 18 out of 25 third-party GitHubAction dependencies pinned
- Info: 0 out of 14 pipCommand dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: SAST tool is not run on all commits -- score normalized to 0
- Warn: 0 commits out of 30 are checked with a SAST tool
Security-Policy10
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: SECURITY.md:1
- Info: Found linked content: SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
CII-Best-Practices5
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning: badge detected: Passing
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
TimescaleDB is an open-source time-series database built on PostgreSQL. It enables fast analytics, efficient storage, and powerful querying for time-series workloads.
Package details
- Extension version
- 2.32.0
- Image built
- Publisher
- cloudnative-pg
- Build
- Debian
- Platform
- PG 18 · Bookworm · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/timescaledb
- Upstream homepage ↗github.com/timescale/timescaledb
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION timescaledb;- SQL version
2.32.0
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'timescaledb' |
These recipe settings are used in automated smoke tests.
OpenSSF scorecard
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.
View information about checks. Automated results are informational only; some categories may not apply to this project.
Scanned · View OpenSSF report ↗
Dangerous-Workflow0
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: dangerous workflow patterns detected
- Warn: untrusted code checkout '${{ github.event.pull_request.head.sha }}': .github/workflows/release_changelog.yml:55
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-Protection3
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection is not maximal on development and all release branches
- Info: 'allow deletion' disabled on branch 'main'
- Info: 'allow deletion' disabled on branch '2.30.x'
- Info: 'allow deletion' disabled on branch '2.26.x'
- Info: 'allow deletion' disabled on branch '2.25.x'
- Info: 'allow deletion' disabled on branch '2.24.x'
- Info: 'allow deletion' disabled on branch '2.23.x'
- Info: 'allow deletion' disabled on branch '2.22.x'
- Info: 'allow deletion' disabled on branch '2.21.x'
- Info: 'force pushes' disabled on branch 'main'
- Info: 'force pushes' disabled on branch '2.30.x'
- Info: 'force pushes' disabled on branch '2.26.x'
- Info: 'force pushes' disabled on branch '2.25.x'
- Info: 'force pushes' disabled on branch '2.24.x'
- Info: 'force pushes' disabled on branch '2.23.x'
- Info: 'force pushes' disabled on branch '2.22.x'
- Info: 'force pushes' disabled on branch '2.21.x'
- Warn: required approving review count is 1 on branch 'main'
- Warn: branch '2.30.x' does not require approvers
- Warn: branch '2.26.x' does not require approvers
- Warn: branch '2.25.x' does not require approvers
- Warn: branch '2.24.x' does not require approvers
- Warn: branch '2.23.x' does not require approvers
- Warn: branch '2.22.x' does not require approvers
- Warn: branch '2.21.x' does not require approvers
- Warn: codeowners review is required - but no codeowners file found in repo
- Warn: codeowners review is not required on branch '2.30.x'
- Warn: codeowners review is not required on branch '2.26.x'
- Warn: codeowners review is not required on branch '2.25.x'
- Warn: codeowners review is not required on branch '2.24.x'
- Warn: codeowners review is not required on branch '2.23.x'
- Warn: codeowners review is not required on branch '2.22.x'
- Warn: codeowners review is not required on branch '2.21.x'
- Info: status check found to merge onto on branch 'main'
- Info: status check found to merge onto on branch '2.30.x'
- Info: status check found to merge onto on branch '2.26.x'
- Info: status check found to merge onto on branch '2.25.x'
- Info: status check found to merge onto on branch '2.24.x'
- Info: status check found to merge onto on branch '2.23.x'
- Info: status check found to merge onto on branch '2.22.x'
- Info: status check found to merge onto on branch '2.21.x'
- Info: PRs are required in order to make changes on branch 'main'
Code-Review10
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: all changesets reviewed
Maintained10
Determines if the project is "actively maintained".
Reasoning: 30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/llm-fuzzer.yaml:80
- Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/llm-fuzzer.yaml:81
- Info: jobLevel 'issues' permission set to 'read': .github/workflows/llm-fuzzer.yaml:82
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/release_sanity.yml:240
- Info: jobLevel 'issues' permission set to 'read': .github/workflows/release_sanity.yml:28
- Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/release_sanity.yml:29
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/release_sanity.yml:27
- Warn: no topLevel permission defined: .github/workflows/abi.yaml:1
- Warn: no topLevel permission defined: .github/workflows/apt-installcheck.yaml:1
- Warn: no topLevel permission defined: .github/workflows/apt-packages.yaml:1
- Warn: no topLevel permission defined: .github/workflows/backport-trigger.yaml:1
- Warn: topLevel 'statuses' permission set to 'write': .github/workflows/backport.yaml:24
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/backport.yaml:20
- Warn: topLevel 'actions' permission set to 'write': .github/workflows/backport.yaml:23
- Info: topLevel 'contents' permission set to 'read': .github/workflows/build-deb-artifacts.yaml:20
- Warn: no topLevel permission defined: .github/workflows/catalog-updates-check.yaml:1
- Warn: no topLevel permission defined: .github/workflows/changelog-check.yaml:1
- Warn: no topLevel permission defined: .github/workflows/coccinelle.yaml:1
- Warn: no topLevel permission defined: .github/workflows/code_style.yaml:1
- Warn: no topLevel permission defined: .github/workflows/docker-images.yaml:1
- Warn: no topLevel permission defined: .github/workflows/extras-diagnostic.yaml:1
- Warn: no topLevel permission defined: .github/workflows/homebrew.yaml:1
- Warn: no topLevel permission defined: .github/workflows/issue-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/label-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/label-released-prs.yaml:1
- Warn: no topLevel permission defined: .github/workflows/libfuzzer.yaml:1
- Warn: no topLevel permission defined: .github/workflows/linux-32bit-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/linux-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/llm-fuzzer.yaml:1
- Warn: no topLevel permission defined: .github/workflows/loader_check.yml:1
- Warn: no topLevel permission defined: .github/workflows/memory-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/nightly_cloud_smoke_test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pg_ladybug.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pg_upgrade-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pgspot.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-approvals.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-validation.yaml:1
- Warn: no topLevel permission defined: .github/workflows/prerelease-sanity.yaml:1
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release_changelog.yml:14
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/release_feature_freeze_ceremony.yaml:26
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/release_post_release_ceremony.yaml:17
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release_release.yml:22
- Warn: no topLevel permission defined: .github/workflows/release_sanity.yml:1
- Warn: no topLevel permission defined: .github/workflows/rpm-packages.yaml:1
- Warn: no topLevel permission defined: .github/workflows/sanitizer-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/shellcheck.yaml:1
- Warn: no topLevel permission defined: .github/workflows/snapshot-abi.yaml:1
- Warn: no topLevel permission defined: .github/workflows/sqlsmith.yaml:1
- Warn: no topLevel permission defined: .github/workflows/stalebot.yaml:1
- Warn: no topLevel permission defined: .github/workflows/tests-fail-on-old-code.yaml:1
- Warn: no topLevel permission defined: .github/workflows/trigger-package-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/trigger-prerelease-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/update-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/windows-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/windows-packages.yaml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies6
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 6
- Info: Possibly incomplete results: error parsing shell code: invalid parameter name: .github/workflows/libfuzzer.yaml:198
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:88
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:94
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:103
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:113
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:119
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:130
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:142
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:150
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:164
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:210
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:216
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:227
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:252
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:256
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:261
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:272
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:279
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:309
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:359
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:377
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:405
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:419
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_release.yml:81: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_release.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:196: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:204: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:212: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:220: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:180: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:188: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: pipCommand not pinned by hash: .github/workflows/backport.yaml:34
- Warn: pipCommand not pinned by hash: .github/workflows/catalog-updates-check.yaml:19
- Warn: pipCommand not pinned by hash: .github/workflows/changelog-check.yaml:32
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:93
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:53
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:16
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:244
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:245
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:250
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:252
- Warn: pipCommand not pinned by hash: .github/workflows/label-released-prs.yaml:28
- Warn: npmCommand not pinned by hash: .github/workflows/llm-fuzzer.yaml:208
- Warn: pipCommand not pinned by hash: .github/workflows/pg_upgrade-test.yaml:77
- Warn: pipCommand not pinned by hash: .github/workflows/pgspot.yaml:52
- Warn: pipCommand not pinned by hash: .github/workflows/release_feature_freeze_ceremony.yaml:103
- Info: 155 out of 155 GitHub-owned GitHubAction dependencies pinned
- Info: 18 out of 25 third-party GitHubAction dependencies pinned
- Info: 0 out of 14 pipCommand dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: SAST tool is not run on all commits -- score normalized to 0
- Warn: 0 commits out of 30 are checked with a SAST tool
Security-Policy10
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: SECURITY.md:1
- Info: Found linked content: SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
CII-Best-Practices5
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning: badge detected: Passing
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
TimescaleDB is an open-source time-series database built on PostgreSQL. It enables fast analytics, efficient storage, and powerful querying for time-series workloads.
Package details
- Extension version
- 2.32.0
- Image built
- Publisher
- cloudnative-pg
- Build
- Debian
- Platform
- PG 18 · Bookworm · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/timescaledb
- Upstream homepage ↗github.com/timescale/timescaledb
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION timescaledb;- SQL version
2.32.0
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'timescaledb' |
These recipe settings are used in automated smoke tests.
OpenSSF scorecard
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.
View information about checks. Automated results are informational only; some categories may not apply to this project.
Scanned · View OpenSSF report ↗
Dangerous-Workflow0
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: dangerous workflow patterns detected
- Warn: untrusted code checkout '${{ github.event.pull_request.head.sha }}': .github/workflows/release_changelog.yml:55
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-Protection3
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection is not maximal on development and all release branches
- Info: 'allow deletion' disabled on branch 'main'
- Info: 'allow deletion' disabled on branch '2.30.x'
- Info: 'allow deletion' disabled on branch '2.26.x'
- Info: 'allow deletion' disabled on branch '2.25.x'
- Info: 'allow deletion' disabled on branch '2.24.x'
- Info: 'allow deletion' disabled on branch '2.23.x'
- Info: 'allow deletion' disabled on branch '2.22.x'
- Info: 'allow deletion' disabled on branch '2.21.x'
- Info: 'force pushes' disabled on branch 'main'
- Info: 'force pushes' disabled on branch '2.30.x'
- Info: 'force pushes' disabled on branch '2.26.x'
- Info: 'force pushes' disabled on branch '2.25.x'
- Info: 'force pushes' disabled on branch '2.24.x'
- Info: 'force pushes' disabled on branch '2.23.x'
- Info: 'force pushes' disabled on branch '2.22.x'
- Info: 'force pushes' disabled on branch '2.21.x'
- Warn: required approving review count is 1 on branch 'main'
- Warn: branch '2.30.x' does not require approvers
- Warn: branch '2.26.x' does not require approvers
- Warn: branch '2.25.x' does not require approvers
- Warn: branch '2.24.x' does not require approvers
- Warn: branch '2.23.x' does not require approvers
- Warn: branch '2.22.x' does not require approvers
- Warn: branch '2.21.x' does not require approvers
- Warn: codeowners review is required - but no codeowners file found in repo
- Warn: codeowners review is not required on branch '2.30.x'
- Warn: codeowners review is not required on branch '2.26.x'
- Warn: codeowners review is not required on branch '2.25.x'
- Warn: codeowners review is not required on branch '2.24.x'
- Warn: codeowners review is not required on branch '2.23.x'
- Warn: codeowners review is not required on branch '2.22.x'
- Warn: codeowners review is not required on branch '2.21.x'
- Info: status check found to merge onto on branch 'main'
- Info: status check found to merge onto on branch '2.30.x'
- Info: status check found to merge onto on branch '2.26.x'
- Info: status check found to merge onto on branch '2.25.x'
- Info: status check found to merge onto on branch '2.24.x'
- Info: status check found to merge onto on branch '2.23.x'
- Info: status check found to merge onto on branch '2.22.x'
- Info: status check found to merge onto on branch '2.21.x'
- Info: PRs are required in order to make changes on branch 'main'
Code-Review10
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: all changesets reviewed
Maintained10
Determines if the project is "actively maintained".
Reasoning: 30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/llm-fuzzer.yaml:80
- Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/llm-fuzzer.yaml:81
- Info: jobLevel 'issues' permission set to 'read': .github/workflows/llm-fuzzer.yaml:82
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/release_sanity.yml:240
- Info: jobLevel 'issues' permission set to 'read': .github/workflows/release_sanity.yml:28
- Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/release_sanity.yml:29
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/release_sanity.yml:27
- Warn: no topLevel permission defined: .github/workflows/abi.yaml:1
- Warn: no topLevel permission defined: .github/workflows/apt-installcheck.yaml:1
- Warn: no topLevel permission defined: .github/workflows/apt-packages.yaml:1
- Warn: no topLevel permission defined: .github/workflows/backport-trigger.yaml:1
- Warn: topLevel 'statuses' permission set to 'write': .github/workflows/backport.yaml:24
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/backport.yaml:20
- Warn: topLevel 'actions' permission set to 'write': .github/workflows/backport.yaml:23
- Info: topLevel 'contents' permission set to 'read': .github/workflows/build-deb-artifacts.yaml:20
- Warn: no topLevel permission defined: .github/workflows/catalog-updates-check.yaml:1
- Warn: no topLevel permission defined: .github/workflows/changelog-check.yaml:1
- Warn: no topLevel permission defined: .github/workflows/coccinelle.yaml:1
- Warn: no topLevel permission defined: .github/workflows/code_style.yaml:1
- Warn: no topLevel permission defined: .github/workflows/docker-images.yaml:1
- Warn: no topLevel permission defined: .github/workflows/extras-diagnostic.yaml:1
- Warn: no topLevel permission defined: .github/workflows/homebrew.yaml:1
- Warn: no topLevel permission defined: .github/workflows/issue-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/label-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/label-released-prs.yaml:1
- Warn: no topLevel permission defined: .github/workflows/libfuzzer.yaml:1
- Warn: no topLevel permission defined: .github/workflows/linux-32bit-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/linux-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/llm-fuzzer.yaml:1
- Warn: no topLevel permission defined: .github/workflows/loader_check.yml:1
- Warn: no topLevel permission defined: .github/workflows/memory-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/nightly_cloud_smoke_test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pg_ladybug.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pg_upgrade-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pgspot.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-approvals.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-handling.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pr-validation.yaml:1
- Warn: no topLevel permission defined: .github/workflows/prerelease-sanity.yaml:1
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release_changelog.yml:14
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/release_feature_freeze_ceremony.yaml:26
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/release_post_release_ceremony.yaml:17
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release_release.yml:22
- Warn: no topLevel permission defined: .github/workflows/release_sanity.yml:1
- Warn: no topLevel permission defined: .github/workflows/rpm-packages.yaml:1
- Warn: no topLevel permission defined: .github/workflows/sanitizer-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/shellcheck.yaml:1
- Warn: no topLevel permission defined: .github/workflows/snapshot-abi.yaml:1
- Warn: no topLevel permission defined: .github/workflows/sqlsmith.yaml:1
- Warn: no topLevel permission defined: .github/workflows/stalebot.yaml:1
- Warn: no topLevel permission defined: .github/workflows/tests-fail-on-old-code.yaml:1
- Warn: no topLevel permission defined: .github/workflows/trigger-package-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/trigger-prerelease-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/update-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/windows-build-and-test.yaml:1
- Warn: no topLevel permission defined: .github/workflows/windows-packages.yaml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies6
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 6
- Info: Possibly incomplete results: error parsing shell code: invalid parameter name: .github/workflows/libfuzzer.yaml:198
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:88
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:94
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:103
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:113
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:119
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:130
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:142
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:150
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:164
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:210
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:216
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:227
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:252
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:256
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:261
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:272
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:279
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:309
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:359
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:377
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:405
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/linux-build-and-test.yaml:419
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_release.yml:81: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_release.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:196: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:204: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:212: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:220: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:180: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release_sanity.yml:188: update your workflow using https://app.stepsecurity.io/secureworkflow/timescale/timescaledb/release_sanity.yml/main?enable=pin
- Warn: pipCommand not pinned by hash: .github/workflows/backport.yaml:34
- Warn: pipCommand not pinned by hash: .github/workflows/catalog-updates-check.yaml:19
- Warn: pipCommand not pinned by hash: .github/workflows/changelog-check.yaml:32
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:93
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:53
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:16
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:244
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:245
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:250
- Warn: pipCommand not pinned by hash: .github/workflows/code_style.yaml:252
- Warn: pipCommand not pinned by hash: .github/workflows/label-released-prs.yaml:28
- Warn: npmCommand not pinned by hash: .github/workflows/llm-fuzzer.yaml:208
- Warn: pipCommand not pinned by hash: .github/workflows/pg_upgrade-test.yaml:77
- Warn: pipCommand not pinned by hash: .github/workflows/pgspot.yaml:52
- Warn: pipCommand not pinned by hash: .github/workflows/release_feature_freeze_ceremony.yaml:103
- Info: 155 out of 155 GitHub-owned GitHubAction dependencies pinned
- Info: 18 out of 25 third-party GitHubAction dependencies pinned
- Info: 0 out of 14 pipCommand dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: SAST tool is not run on all commits -- score normalized to 0
- Warn: 0 commits out of 30 are checked with a SAST tool
Security-Policy10
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: SECURITY.md:1
- Info: Found linked content: SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
CII-Best-Practices5
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning: badge detected: Passing
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Dependencies
Packages shipped in this image, including the extension itself.
This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.
Dependencies
Packages shipped in this image, including the extension itself.
This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.
Dependencies
Packages shipped in this image, including the extension itself.
This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.
Dependencies
Packages shipped in this image, including the extension itself.
This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-timescaledb/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: timescaledb Source: https://github.com/timescale/timescaledb Files-Excluded: tsl scripts/c_license_header-timescale.h scripts/license_tsl.spec scripts/sql_license_tsl.sql Files: * Copyright: Copyright (c) 2017-2022 Timescale, Inc. All Rights Reserved. Copyright (c) 2016-2017 440 Labs, Inc. dba Timescale. All Rights Reserved. Portions Copyright (c) 1996-2024, PostgreSQL Global Development Group Portions Copyright (c) 1994, The Regents of the University of California License: Apache-2.0 and PostgreSQL Source code in this repository is variously licensed under the Apache License Version 2.0, an Apache compatible license, or the Timescale License. . All source code should have information at the beginning of its respective file which specifies its licensing information. . * Outside of the "tsl" directory, source code in a given file is licensed under the Apache License Version 2.0, unless otherwise noted (e.g., an Apache-compatible license). . * Within the "tsl" folder, source code in a given file is licensed under the Timescale License, unless otherwise noted. . The tsl folder has been removed when creating the +dfsg orig tarballs for Debian. No tsl-licensed code remains. . Certain files in this code base have been modified and/or copied, either partially or wholely, from source code from the PostgreSQL database management system License: Apache-2.0 On Debian systems, the Apache 2.0 license is located in /usr/share/common-licenses/Apache-2.0. License: PostgreSQL Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 80017903cc13cee3ff2f50ff0a52157e612d44abb22000a3e5379df62d75fa64
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-timescaledb/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: timescaledb Source: https://github.com/timescale/timescaledb Files-Excluded: tsl scripts/c_license_header-timescale.h scripts/license_tsl.spec scripts/sql_license_tsl.sql Files: * Copyright: Copyright (c) 2017-2022 Timescale, Inc. All Rights Reserved. Copyright (c) 2016-2017 440 Labs, Inc. dba Timescale. All Rights Reserved. Portions Copyright (c) 1996-2024, PostgreSQL Global Development Group Portions Copyright (c) 1994, The Regents of the University of California License: Apache-2.0 and PostgreSQL Source code in this repository is variously licensed under the Apache License Version 2.0, an Apache compatible license, or the Timescale License. . All source code should have information at the beginning of its respective file which specifies its licensing information. . * Outside of the "tsl" directory, source code in a given file is licensed under the Apache License Version 2.0, unless otherwise noted (e.g., an Apache-compatible license). . * Within the "tsl" folder, source code in a given file is licensed under the Timescale License, unless otherwise noted. . The tsl folder has been removed when creating the +dfsg orig tarballs for Debian. No tsl-licensed code remains. . Certain files in this code base have been modified and/or copied, either partially or wholely, from source code from the PostgreSQL database management system License: Apache-2.0 On Debian systems, the Apache 2.0 license is located in /usr/share/common-licenses/Apache-2.0. License: PostgreSQL Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 80017903cc13cee3ff2f50ff0a52157e612d44abb22000a3e5379df62d75fa64
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-timescaledb/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: timescaledb Source: https://github.com/timescale/timescaledb Files-Excluded: tsl scripts/c_license_header-timescale.h scripts/license_tsl.spec scripts/sql_license_tsl.sql Files: * Copyright: Copyright (c) 2017-2022 Timescale, Inc. All Rights Reserved. Copyright (c) 2016-2017 440 Labs, Inc. dba Timescale. All Rights Reserved. Portions Copyright (c) 1996-2024, PostgreSQL Global Development Group Portions Copyright (c) 1994, The Regents of the University of California License: Apache-2.0 and PostgreSQL Source code in this repository is variously licensed under the Apache License Version 2.0, an Apache compatible license, or the Timescale License. . All source code should have information at the beginning of its respective file which specifies its licensing information. . * Outside of the "tsl" directory, source code in a given file is licensed under the Apache License Version 2.0, unless otherwise noted (e.g., an Apache-compatible license). . * Within the "tsl" folder, source code in a given file is licensed under the Timescale License, unless otherwise noted. . The tsl folder has been removed when creating the +dfsg orig tarballs for Debian. No tsl-licensed code remains. . Certain files in this code base have been modified and/or copied, either partially or wholely, from source code from the PostgreSQL database management system License: Apache-2.0 On Debian systems, the Apache 2.0 license is located in /usr/share/common-licenses/Apache-2.0. License: PostgreSQL Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 80017903cc13cee3ff2f50ff0a52157e612d44abb22000a3e5379df62d75fa64
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-timescaledb/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: timescaledb Source: https://github.com/timescale/timescaledb Files-Excluded: tsl scripts/c_license_header-timescale.h scripts/license_tsl.spec scripts/sql_license_tsl.sql Files: * Copyright: Copyright (c) 2017-2022 Timescale, Inc. All Rights Reserved. Copyright (c) 2016-2017 440 Labs, Inc. dba Timescale. All Rights Reserved. Portions Copyright (c) 1996-2024, PostgreSQL Global Development Group Portions Copyright (c) 1994, The Regents of the University of California License: Apache-2.0 and PostgreSQL Source code in this repository is variously licensed under the Apache License Version 2.0, an Apache compatible license, or the Timescale License. . All source code should have information at the beginning of its respective file which specifies its licensing information. . * Outside of the "tsl" directory, source code in a given file is licensed under the Apache License Version 2.0, unless otherwise noted (e.g., an Apache-compatible license). . * Within the "tsl" folder, source code in a given file is licensed under the Timescale License, unless otherwise noted. . The tsl folder has been removed when creating the +dfsg orig tarballs for Debian. No tsl-licensed code remains. . Certain files in this code base have been modified and/or copied, either partially or wholely, from source code from the PostgreSQL database management system License: Apache-2.0 On Debian systems, the Apache 2.0 license is located in /usr/share/common-licenses/Apache-2.0. License: PostgreSQL Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 80017903cc13cee3ff2f50ff0a52157e612d44abb22000a3e5379df62d75fa64
Versions
Extension versions and the images built from them.
Tagged GHCR builds fetched .
