← Browse the extensions catalog

pg-durable

Source README ↗

Overview

pg_durable is a PostgreSQL extension for durable, fault-tolerant SQL workflows. It checkpoints composable SQL steps in PostgreSQL so executions can resume after crashes, restarts, or failed steps, without an external orchestration service. This image supports PostgreSQL 18 on Debian bookworm and trixie.

Package details

Extension version
0.2.9
Image built
Publisher
cnpg-extensions
Build
PGRX
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 pg_durable;
SQL version
0.2.9

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_durable'
pg_durable.databaseapp

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 · Download cached scan ↓

Dangerous-Workflow10

Determines if the project's GitHub Action workflows avoid dangerous patterns.

Reasoning: no dangerous workflow patterns detected

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-Protection6

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: 'force pushes' disabled on branch 'main'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'main'
  • Warn: required approving review count is 1 on branch 'main'
  • Warn: codeowners review is not required on branch 'main'
  • Warn: no status checks found to merge onto branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review3

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

Reasoning: Found 8/26 approved changesets -- score normalized to 3

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: .github/dependabot.yml:1

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 30 commit(s) and 0 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/ci.yml:197
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/copilot-setup-steps.yml:22
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/docker.yml:45
  • Warn: jobLevel 'contents' permission set to 'write': .github/workflows/package-release.yml:289
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/prebuild.yml:23
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/prebuild.yml:66
  • Warn: no topLevel permission defined: .github/workflows/ci.yml:1
  • Warn: no topLevel permission defined: .github/workflows/copilot-setup-steps.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/docker-publish.yml:40
  • Warn: topLevel 'packages' permission set to 'write': .github/workflows/docker-publish.yml:41
  • Warn: no topLevel permission defined: .github/workflows/docker.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/package-release.yml:30
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pages.yml:13
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pgxn-publish.yml:30
  • Warn: no topLevel permission defined: .github/workflows/prebuild.yml:1

Check details ↗

Vulnerabilities4

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 6 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0543
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0459
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2024-0436
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2023-0071
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-Dependencies8

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: dependency not pinned by hash detected -- score normalized to 8

  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-e2e-docker.sh:201
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: tests/e2e/run.sh:55
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker-publish.yml:250
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker-publish.yml:257
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker.yml:100
  • Warn: containerImage not pinned by hash: Dockerfile:6: pin your Docker image by updating rust:bookworm to rust:bookworm@sha256:ade39a710ef85f3506cffcfec3e8a24ba090badef1dff2fb798f71d878833fea
  • Warn: containerImage not pinned by hash: Dockerfile:51: pin your Docker image by updating postgres:17-bookworm to postgres:17-bookworm@sha256:40865bc877a289da75963d97d72b59633f639fc5af7a4e856bfa3714cae5b536
  • Warn: containerImage not pinned by hash: Dockerfile.release:18: pin your Docker image by updating postgres:17-bookworm to postgres:17-bookworm@sha256:40865bc877a289da75963d97d72b59633f639fc5af7a4e856bfa3714cae5b536
  • Info: 42 out of 42 GitHub-owned GitHubAction dependencies pinned
  • Info: 7 out of 7 third-party GitHubAction dependencies pinned
  • Info: 0 out of 3 containerImage 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 ↗

CI-Tests9

Determines if the project runs tests before pull requests are merged.

Reasoning: 29 out of 30 merged PRs checked by a CI test -- score normalized to 9

Check details ↗

CII-Best-Practices0

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

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

Reasoning: project has 5 contributing companies or organizations

  • Info: found contributions from: apache, coursera-dl, docker-flink, microsoft, weblabdeusto

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.txt:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • MIT OR Apache-2.0122 packages
  • MIT53 packages
  • Unicode-3.015 packages
  • Apache-2.0 OR MIT14 packages
  • Apache-2.02 packages
  • Unlicense OR MIT2 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
  • 0BSD OR MIT OR Apache-2.01 package
9 more license expressions
  • Apache-2.0 OR BSL-1.0 OR MIT1 package
  • BSD-2-Clause OR Apache-2.0 OR MIT1 package
  • BSD-3-Clause1 package
  • GPL-2.0-only AND GPL-2.0-or-later AND LicenseRef-verbatim1 package
  • MIT OR Apache-2.0 OR Zlib1 package
  • MIT OR Zlib OR Apache-2.01 package
  • PostgreSQL1 package
  • Zlib1 package
  • Zlib OR Apache-2.0 OR MIT1 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

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

Evidence

Overview

pg_durable is a PostgreSQL extension for durable, fault-tolerant SQL workflows. It checkpoints composable SQL steps in PostgreSQL so executions can resume after crashes, restarts, or failed steps, without an external orchestration service. This image supports PostgreSQL 18 on Debian bookworm and trixie.

Package details

Extension version
0.2.9
Image built
Publisher
cnpg-extensions
Build
PGRX
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 pg_durable;
SQL version
0.2.9

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_durable'
pg_durable.databaseapp

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 · Download cached scan ↓

Dangerous-Workflow10

Determines if the project's GitHub Action workflows avoid dangerous patterns.

Reasoning: no dangerous workflow patterns detected

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-Protection6

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: 'force pushes' disabled on branch 'main'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'main'
  • Warn: required approving review count is 1 on branch 'main'
  • Warn: codeowners review is not required on branch 'main'
  • Warn: no status checks found to merge onto branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review3

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

Reasoning: Found 8/26 approved changesets -- score normalized to 3

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: .github/dependabot.yml:1

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 30 commit(s) and 0 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/ci.yml:197
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/copilot-setup-steps.yml:22
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/docker.yml:45
  • Warn: jobLevel 'contents' permission set to 'write': .github/workflows/package-release.yml:289
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/prebuild.yml:23
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/prebuild.yml:66
  • Warn: no topLevel permission defined: .github/workflows/ci.yml:1
  • Warn: no topLevel permission defined: .github/workflows/copilot-setup-steps.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/docker-publish.yml:40
  • Warn: topLevel 'packages' permission set to 'write': .github/workflows/docker-publish.yml:41
  • Warn: no topLevel permission defined: .github/workflows/docker.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/package-release.yml:30
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pages.yml:13
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pgxn-publish.yml:30
  • Warn: no topLevel permission defined: .github/workflows/prebuild.yml:1

Check details ↗

Vulnerabilities4

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 6 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0543
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0459
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2024-0436
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2023-0071
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-Dependencies8

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: dependency not pinned by hash detected -- score normalized to 8

  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-e2e-docker.sh:201
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: tests/e2e/run.sh:55
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker-publish.yml:250
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker-publish.yml:257
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker.yml:100
  • Warn: containerImage not pinned by hash: Dockerfile:6: pin your Docker image by updating rust:bookworm to rust:bookworm@sha256:ade39a710ef85f3506cffcfec3e8a24ba090badef1dff2fb798f71d878833fea
  • Warn: containerImage not pinned by hash: Dockerfile:51: pin your Docker image by updating postgres:17-bookworm to postgres:17-bookworm@sha256:40865bc877a289da75963d97d72b59633f639fc5af7a4e856bfa3714cae5b536
  • Warn: containerImage not pinned by hash: Dockerfile.release:18: pin your Docker image by updating postgres:17-bookworm to postgres:17-bookworm@sha256:40865bc877a289da75963d97d72b59633f639fc5af7a4e856bfa3714cae5b536
  • Info: 42 out of 42 GitHub-owned GitHubAction dependencies pinned
  • Info: 7 out of 7 third-party GitHubAction dependencies pinned
  • Info: 0 out of 3 containerImage 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 ↗

CI-Tests9

Determines if the project runs tests before pull requests are merged.

Reasoning: 29 out of 30 merged PRs checked by a CI test -- score normalized to 9

Check details ↗

CII-Best-Practices0

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

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

Reasoning: project has 5 contributing companies or organizations

  • Info: found contributions from: apache, coursera-dl, docker-flink, microsoft, weblabdeusto

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.txt:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • MIT OR Apache-2.0121 packages
  • MIT53 packages
  • Unicode-3.015 packages
  • Apache-2.0 OR MIT14 packages
  • Apache-2.02 packages
  • Unlicense OR MIT2 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
  • 0BSD OR MIT OR Apache-2.01 package
9 more license expressions
  • Apache-2.0 OR BSL-1.0 OR MIT1 package
  • BSD-2-Clause OR Apache-2.0 OR MIT1 package
  • BSD-3-Clause1 package
  • GPL-2.0-only AND GPL-2.0-or-later AND LicenseRef-verbatim1 package
  • MIT OR Apache-2.0 OR Zlib1 package
  • MIT OR Zlib OR Apache-2.01 package
  • PostgreSQL1 package
  • Zlib1 package
  • Zlib OR Apache-2.0 OR MIT1 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

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

Evidence

Overview

pg_durable is a PostgreSQL extension for durable, fault-tolerant SQL workflows. It checkpoints composable SQL steps in PostgreSQL so executions can resume after crashes, restarts, or failed steps, without an external orchestration service. This image supports PostgreSQL 18 on Debian bookworm and trixie.

Package details

Extension version
0.2.9
Image built
Publisher
cnpg-extensions
Build
PGRX
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 pg_durable;
SQL version
0.2.9

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_durable'
pg_durable.databaseapp

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 · Download cached scan ↓

Dangerous-Workflow10

Determines if the project's GitHub Action workflows avoid dangerous patterns.

Reasoning: no dangerous workflow patterns detected

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-Protection6

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: 'force pushes' disabled on branch 'main'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'main'
  • Warn: required approving review count is 1 on branch 'main'
  • Warn: codeowners review is not required on branch 'main'
  • Warn: no status checks found to merge onto branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review3

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

Reasoning: Found 8/26 approved changesets -- score normalized to 3

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: .github/dependabot.yml:1

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 30 commit(s) and 0 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/ci.yml:197
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/copilot-setup-steps.yml:22
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/docker.yml:45
  • Warn: jobLevel 'contents' permission set to 'write': .github/workflows/package-release.yml:289
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/prebuild.yml:23
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/prebuild.yml:66
  • Warn: no topLevel permission defined: .github/workflows/ci.yml:1
  • Warn: no topLevel permission defined: .github/workflows/copilot-setup-steps.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/docker-publish.yml:40
  • Warn: topLevel 'packages' permission set to 'write': .github/workflows/docker-publish.yml:41
  • Warn: no topLevel permission defined: .github/workflows/docker.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/package-release.yml:30
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pages.yml:13
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pgxn-publish.yml:30
  • Warn: no topLevel permission defined: .github/workflows/prebuild.yml:1

Check details ↗

Vulnerabilities4

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 6 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0543
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0459
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2024-0436
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2023-0071
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-Dependencies8

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: dependency not pinned by hash detected -- score normalized to 8

  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-e2e-docker.sh:201
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: tests/e2e/run.sh:55
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker-publish.yml:250
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker-publish.yml:257
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker.yml:100
  • Warn: containerImage not pinned by hash: Dockerfile:6: pin your Docker image by updating rust:bookworm to rust:bookworm@sha256:ade39a710ef85f3506cffcfec3e8a24ba090badef1dff2fb798f71d878833fea
  • Warn: containerImage not pinned by hash: Dockerfile:51: pin your Docker image by updating postgres:17-bookworm to postgres:17-bookworm@sha256:40865bc877a289da75963d97d72b59633f639fc5af7a4e856bfa3714cae5b536
  • Warn: containerImage not pinned by hash: Dockerfile.release:18: pin your Docker image by updating postgres:17-bookworm to postgres:17-bookworm@sha256:40865bc877a289da75963d97d72b59633f639fc5af7a4e856bfa3714cae5b536
  • Info: 42 out of 42 GitHub-owned GitHubAction dependencies pinned
  • Info: 7 out of 7 third-party GitHubAction dependencies pinned
  • Info: 0 out of 3 containerImage 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 ↗

CI-Tests9

Determines if the project runs tests before pull requests are merged.

Reasoning: 29 out of 30 merged PRs checked by a CI test -- score normalized to 9

Check details ↗

CII-Best-Practices0

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

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

Reasoning: project has 5 contributing companies or organizations

  • Info: found contributions from: apache, coursera-dl, docker-flink, microsoft, weblabdeusto

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.txt:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • MIT OR Apache-2.0122 packages
  • MIT53 packages
  • Unicode-3.015 packages
  • Apache-2.0 OR MIT14 packages
  • Apache-2.02 packages
  • Unlicense OR MIT2 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
  • 0BSD OR MIT OR Apache-2.01 package
9 more license expressions
  • Apache-2.0 OR BSL-1.0 OR MIT1 package
  • BSD-2-Clause OR Apache-2.0 OR MIT1 package
  • BSD-3-Clause1 package
  • LicenseRef-fd7e4aae7e7b05f217bcf2d02322825c360e66c52c4c2f1b28d784d6297a1c231 package
  • MIT OR Apache-2.0 OR Zlib1 package
  • MIT OR Zlib OR Apache-2.01 package
  • PostgreSQL1 package
  • Zlib1 package
  • Zlib OR Apache-2.0 OR MIT1 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

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

Evidence

Overview

pg_durable is a PostgreSQL extension for durable, fault-tolerant SQL workflows. It checkpoints composable SQL steps in PostgreSQL so executions can resume after crashes, restarts, or failed steps, without an external orchestration service. This image supports PostgreSQL 18 on Debian bookworm and trixie.

Package details

Extension version
0.2.9
Image built
Publisher
cnpg-extensions
Build
PGRX
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 pg_durable;
SQL version
0.2.9

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_durable'
pg_durable.databaseapp

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 · Download cached scan ↓

Dangerous-Workflow10

Determines if the project's GitHub Action workflows avoid dangerous patterns.

Reasoning: no dangerous workflow patterns detected

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-Protection6

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: 'force pushes' disabled on branch 'main'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'main'
  • Warn: required approving review count is 1 on branch 'main'
  • Warn: codeowners review is not required on branch 'main'
  • Warn: no status checks found to merge onto branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review3

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

Reasoning: Found 8/26 approved changesets -- score normalized to 3

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: .github/dependabot.yml:1

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 30 commit(s) and 0 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/ci.yml:197
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/copilot-setup-steps.yml:22
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/docker.yml:45
  • Warn: jobLevel 'contents' permission set to 'write': .github/workflows/package-release.yml:289
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/prebuild.yml:23
  • Info: jobLevel 'contents' permission set to 'read': .github/workflows/prebuild.yml:66
  • Warn: no topLevel permission defined: .github/workflows/ci.yml:1
  • Warn: no topLevel permission defined: .github/workflows/copilot-setup-steps.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/docker-publish.yml:40
  • Warn: topLevel 'packages' permission set to 'write': .github/workflows/docker-publish.yml:41
  • Warn: no topLevel permission defined: .github/workflows/docker.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/package-release.yml:30
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pages.yml:13
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pgxn-publish.yml:30
  • Warn: no topLevel permission defined: .github/workflows/prebuild.yml:1

Check details ↗

Vulnerabilities4

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 6 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0543
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0459
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2024-0436
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2023-0071
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-Dependencies8

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: dependency not pinned by hash detected -- score normalized to 8

  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-e2e-docker.sh:201
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: tests/e2e/run.sh:55
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker-publish.yml:250
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker-publish.yml:257
  • Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/docker.yml:100
  • Warn: containerImage not pinned by hash: Dockerfile:6: pin your Docker image by updating rust:bookworm to rust:bookworm@sha256:ade39a710ef85f3506cffcfec3e8a24ba090badef1dff2fb798f71d878833fea
  • Warn: containerImage not pinned by hash: Dockerfile:51: pin your Docker image by updating postgres:17-bookworm to postgres:17-bookworm@sha256:40865bc877a289da75963d97d72b59633f639fc5af7a4e856bfa3714cae5b536
  • Warn: containerImage not pinned by hash: Dockerfile.release:18: pin your Docker image by updating postgres:17-bookworm to postgres:17-bookworm@sha256:40865bc877a289da75963d97d72b59633f639fc5af7a4e856bfa3714cae5b536
  • Info: 42 out of 42 GitHub-owned GitHubAction dependencies pinned
  • Info: 7 out of 7 third-party GitHubAction dependencies pinned
  • Info: 0 out of 3 containerImage 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 ↗

CI-Tests9

Determines if the project runs tests before pull requests are merged.

Reasoning: 29 out of 30 merged PRs checked by a CI test -- score normalized to 9

Check details ↗

CII-Best-Practices0

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

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

Reasoning: project has 5 contributing companies or organizations

  • Info: found contributions from: apache, coursera-dl, docker-flink, microsoft, weblabdeusto

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.txt:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • MIT OR Apache-2.0121 packages
  • MIT53 packages
  • Unicode-3.015 packages
  • Apache-2.0 OR MIT14 packages
  • Apache-2.02 packages
  • Unlicense OR MIT2 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
  • 0BSD OR MIT OR Apache-2.01 package
9 more license expressions
  • Apache-2.0 OR BSL-1.0 OR MIT1 package
  • BSD-2-Clause OR Apache-2.0 OR MIT1 package
  • BSD-3-Clause1 package
  • LicenseRef-fd7e4aae7e7b05f217bcf2d02322825c360e66c52c4c2f1b28d784d6297a1c231 package
  • MIT OR Apache-2.0 OR Zlib1 package
  • MIT OR Zlib OR Apache-2.01 package
  • PostgreSQL1 package
  • Zlib1 package
  • Zlib OR Apache-2.0 OR MIT1 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

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

Evidence