← Browse the extensions catalog

timescaledb-oss

Source README ↗

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

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

ParameterValue
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

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

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'

Check details ↗

Code-Review10

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

Reasoning: all changesets reviewed

Check details ↗

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

Check details ↗

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

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

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

Check details ↗

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

Check details ↗

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

Check details ↗

CII-Best-Practices5

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: badge detected: Passing

Check details ↗

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.

Check details ↗

Extension recipe
Apache-2.0PostgreSQL

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

Image license files

View files →

1 file read directly from /licenses in the selected image. Browse their original contents and checksums in the Licenses tab.

Evidence

Unavailable

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

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

ParameterValue
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

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

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'

Check details ↗

Code-Review10

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

Reasoning: all changesets reviewed

Check details ↗

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

Check details ↗

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

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

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

Check details ↗

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

Check details ↗

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

Check details ↗

CII-Best-Practices5

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: badge detected: Passing

Check details ↗

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.

Check details ↗

Extension recipe
Apache-2.0PostgreSQL

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

Image license files

View files →

1 file read directly from /licenses in the selected image. Browse their original contents and checksums in the Licenses tab.

Evidence

Unavailable

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

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

ParameterValue
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

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

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'

Check details ↗

Code-Review10

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

Reasoning: all changesets reviewed

Check details ↗

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

Check details ↗

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

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

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

Check details ↗

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

Check details ↗

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

Check details ↗

CII-Best-Practices5

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: badge detected: Passing

Check details ↗

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.

Check details ↗

Extension recipe
Apache-2.0PostgreSQL

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

Image license files

View files →

1 file read directly from /licenses in the selected image. Browse their original contents and checksums in the Licenses tab.

Evidence

Unavailable

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

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

ParameterValue
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

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

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'

Check details ↗

Code-Review10

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

Reasoning: all changesets reviewed

Check details ↗

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

Check details ↗

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

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

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

Check details ↗

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

Check details ↗

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

Check details ↗

CII-Best-Practices5

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: badge detected: Passing

Check details ↗

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.

Check details ↗

Extension recipe
Apache-2.0PostgreSQL

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

Image license files

View files →

1 file read directly from /licenses in the selected image. Browse their original contents and checksums in the Licenses tab.

Evidence

Unavailable