pg-background
pg-background
pg_background runs SQL in PostgreSQL background workers and returns completion metadata to the calling session. It does not require shared_preload_libraries; preloading is only needed if you want to set its GUCs in server configuration before first use.
Follow the quick start to set up extension-update email
alerts first, then use the CronJob to install and refresh the catalog. These
examples inherit image references and runtime settings from the catalog. The Cluster YAML
is an excerpt: replace imageCatalogRef: ... with your catalog reference and
keep your existing instance and storage settings.
Usage
1. Add the pg-background extension image to your Cluster
Add the extension image to a complete Cluster definition:
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
name: cluster-pg-background
spec:
imageCatalogRef: ...
postgresql:
extensions:
- name: pg-background
2. Enable the extension in a database
Once the extension's files are available in the cluster, you can install it in a database in either of two ways:
- Declaratively, using a CloudNativePG
Databaseresource. - Through SQL, by running
CREATE EXTENSION pg_background;in the target database.
Platform teams may make extension containers available across their clusters without installing every extension in every database. Install only the extensions a database uses; letting users enable them through SQL alongside the rest of their DDL schema management code can be a convenient approach.
For extensions that normally require superuser privileges, platform teams can use pgextwlist to allow non-superusers to install an administrator-approved selection of extensions.
3. Verify installation
Connect to the database with psql and run \dx to check the installed extensions.
A superuser can run SQL in a background worker and inspect its completion metadata:
SELECT * FROM pg_background_run('SELECT count(*) FROM pg_class');
Use the function in FROM so it executes once. Expanding
(pg_background_run(...)).* in the select list can execute it once per output
column. The command runs in a separate worker. Grant only the privileges needed by the SQL being run; background execution does not bypass PostgreSQL authorization.
Supported matrix and licenses
The image supports PostgreSQL 18 on Debian Bookworm and Trixie. Package copyright is included under /licenses/postgresql-18-pg-background/. PGDG package updates are tracked by Renovate.
Overview
pg_background runs SQL in PostgreSQL background workers and returns completion metadata to the calling session. It does not require shared_preload_libraries ; preloading is only needed if you want to set its GUCs in server configuration before first use.
Package details
- Extension version
- 2.0.3
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Trixie · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-background
- Upstream homepage ↗github.com/vibhorkum/pg_background
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_background;- SQL version
2.0— differs from extension version 2.0.3
PostgreSQL parameters
None specified
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-Workflow10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no dangerous workflow patterns detected
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-Protection0
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection not enabled on development/release branches
- Warn: branch protection not enabled for branch '2.0.3'
- Warn: branch protection not enabled for branch 'v1.6'
- Warn: branch protection not enabled for branch 'v1.5'
- Warn: branch protection not enabled for branch 'v1.1'
- Info: 'allow deletion' disabled on branch 'master'
- Info: 'force pushes' disabled on branch 'master'
- Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
- Warn: required approving review count is 1 on branch 'master'
- Warn: codeowners review is not required on branch 'master'
- Warn: no status checks found to merge onto branch 'master'
- Info: PRs are required in order to make changes on branch 'master'
Code-Review7
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 8/11 approved changesets -- score normalized to 7
Maintained10
Determines if the project is "actively maintained".
Reasoning: 24 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Info: jobLevel 'actions' permission set to 'read': .github/workflows/ci.yml:474
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/ci.yml:475
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies0
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 0
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-local.sh:119
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-relocatable.sh:91
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-upgrade.sh:137
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/ci.yml:69
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:247: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:278: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:304: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:328: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:348: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:397: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:479: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:482: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:537: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Info: 0 out of 11 GitHub-owned GitHubAction dependencies pinned
SAST9
Determines if the project uses static code analysis.
Reasoning: SAST tool detected but not run on all commits
- Info: SAST configuration detected: CodeQL
- Warn: 27 commits out of 30 are checked with a SAST tool
Security-Policy10
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: docs/SECURITY.md:1
- Info: Found linked content: docs/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: docs/SECURITY.md:1
- Info: Found text in security policy: docs/SECURITY.md:1
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
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
pg_background runs SQL in PostgreSQL background workers and returns completion metadata to the calling session. It does not require shared_preload_libraries ; preloading is only needed if you want to set its GUCs in server configuration before first use.
Package details
- Extension version
- 2.0.3
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Trixie · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-background
- Upstream homepage ↗github.com/vibhorkum/pg_background
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_background;- SQL version
2.0— differs from extension version 2.0.3
PostgreSQL parameters
None specified
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-Workflow10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no dangerous workflow patterns detected
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-Protection0
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection not enabled on development/release branches
- Warn: branch protection not enabled for branch '2.0.3'
- Warn: branch protection not enabled for branch 'v1.6'
- Warn: branch protection not enabled for branch 'v1.5'
- Warn: branch protection not enabled for branch 'v1.1'
- Info: 'allow deletion' disabled on branch 'master'
- Info: 'force pushes' disabled on branch 'master'
- Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
- Warn: required approving review count is 1 on branch 'master'
- Warn: codeowners review is not required on branch 'master'
- Warn: no status checks found to merge onto branch 'master'
- Info: PRs are required in order to make changes on branch 'master'
Code-Review7
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 8/11 approved changesets -- score normalized to 7
Maintained10
Determines if the project is "actively maintained".
Reasoning: 24 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Info: jobLevel 'actions' permission set to 'read': .github/workflows/ci.yml:474
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/ci.yml:475
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies0
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 0
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-local.sh:119
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-relocatable.sh:91
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-upgrade.sh:137
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/ci.yml:69
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:247: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:278: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:304: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:328: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:348: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:397: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:479: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:482: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:537: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Info: 0 out of 11 GitHub-owned GitHubAction dependencies pinned
SAST9
Determines if the project uses static code analysis.
Reasoning: SAST tool detected but not run on all commits
- Info: SAST configuration detected: CodeQL
- Warn: 27 commits out of 30 are checked with a SAST tool
Security-Policy10
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: docs/SECURITY.md:1
- Info: Found linked content: docs/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: docs/SECURITY.md:1
- Info: Found text in security policy: docs/SECURITY.md:1
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
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
pg_background runs SQL in PostgreSQL background workers and returns completion metadata to the calling session. It does not require shared_preload_libraries ; preloading is only needed if you want to set its GUCs in server configuration before first use.
Package details
- Extension version
- 2.0.3
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Bookworm · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-background
- Upstream homepage ↗github.com/vibhorkum/pg_background
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_background;- SQL version
2.0— differs from extension version 2.0.3
PostgreSQL parameters
None specified
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-Workflow10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no dangerous workflow patterns detected
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-Protection0
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection not enabled on development/release branches
- Warn: branch protection not enabled for branch '2.0.3'
- Warn: branch protection not enabled for branch 'v1.6'
- Warn: branch protection not enabled for branch 'v1.5'
- Warn: branch protection not enabled for branch 'v1.1'
- Info: 'allow deletion' disabled on branch 'master'
- Info: 'force pushes' disabled on branch 'master'
- Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
- Warn: required approving review count is 1 on branch 'master'
- Warn: codeowners review is not required on branch 'master'
- Warn: no status checks found to merge onto branch 'master'
- Info: PRs are required in order to make changes on branch 'master'
Code-Review7
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 8/11 approved changesets -- score normalized to 7
Maintained10
Determines if the project is "actively maintained".
Reasoning: 24 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Info: jobLevel 'actions' permission set to 'read': .github/workflows/ci.yml:474
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/ci.yml:475
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies0
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 0
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-local.sh:119
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-relocatable.sh:91
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-upgrade.sh:137
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/ci.yml:69
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:247: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:278: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:304: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:328: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:348: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:397: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:479: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:482: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:537: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Info: 0 out of 11 GitHub-owned GitHubAction dependencies pinned
SAST9
Determines if the project uses static code analysis.
Reasoning: SAST tool detected but not run on all commits
- Info: SAST configuration detected: CodeQL
- Warn: 27 commits out of 30 are checked with a SAST tool
Security-Policy10
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: docs/SECURITY.md:1
- Info: Found linked content: docs/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: docs/SECURITY.md:1
- Info: Found text in security policy: docs/SECURITY.md:1
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
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
pg_background runs SQL in PostgreSQL background workers and returns completion metadata to the calling session. It does not require shared_preload_libraries ; preloading is only needed if you want to set its GUCs in server configuration before first use.
Package details
- Extension version
- 2.0.3
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Bookworm · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-background
- Upstream homepage ↗github.com/vibhorkum/pg_background
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_background;- SQL version
2.0— differs from extension version 2.0.3
PostgreSQL parameters
None specified
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-Workflow10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no dangerous workflow patterns detected
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-Protection0
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection not enabled on development/release branches
- Warn: branch protection not enabled for branch '2.0.3'
- Warn: branch protection not enabled for branch 'v1.6'
- Warn: branch protection not enabled for branch 'v1.5'
- Warn: branch protection not enabled for branch 'v1.1'
- Info: 'allow deletion' disabled on branch 'master'
- Info: 'force pushes' disabled on branch 'master'
- Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
- Warn: required approving review count is 1 on branch 'master'
- Warn: codeowners review is not required on branch 'master'
- Warn: no status checks found to merge onto branch 'master'
- Info: PRs are required in order to make changes on branch 'master'
Code-Review7
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 8/11 approved changesets -- score normalized to 7
Maintained10
Determines if the project is "actively maintained".
Reasoning: 24 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Info: jobLevel 'actions' permission set to 'read': .github/workflows/ci.yml:474
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/ci.yml:475
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies0
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 0
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-local.sh:119
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-relocatable.sh:91
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: scripts/test-upgrade.sh:137
- Info: Possibly incomplete results: error parsing shell code: a command can only contain words and redirects; encountered `(`: .github/workflows/ci.yml:69
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:247: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:278: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:304: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:328: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:348: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:397: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:479: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:482: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:537: update your workflow using https://app.stepsecurity.io/secureworkflow/vibhorkum/pg_background/ci.yml/master?enable=pin
- Info: 0 out of 11 GitHub-owned GitHubAction dependencies pinned
SAST9
Determines if the project uses static code analysis.
Reasoning: SAST tool detected but not run on all commits
- Info: SAST configuration detected: CodeQL
- Warn: 27 commits out of 30 are checked with a SAST tool
Security-Policy10
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: docs/SECURITY.md:1
- Info: Found linked content: docs/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: docs/SECURITY.md:1
- Info: Found text in security policy: docs/SECURITY.md:1
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
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Dependencies
Packages shipped in this image, including the extension itself.
1 packages · Scanned
| Package / installed version | License evidence | Advisories |
|---|---|---|
postgresql-18-pg-background ↗ 2.0.3-1.pgdg13+3 | PostgreSQL | No ↗ |
No packages match these filters. Try a different name or license, or clear the filters.
Dependencies
Packages shipped in this image, including the extension itself.
1 packages · Scanned
| Package / installed version | License evidence | Advisories |
|---|---|---|
postgresql-18-pg-background ↗ 2.0.3-1.pgdg13+3 | PostgreSQL | No ↗ |
No packages match these filters. Try a different name or license, or clear the filters.
Dependencies
Packages shipped in this image, including the extension itself.
1 packages · Scanned
| Package / installed version | License evidence | Advisories |
|---|---|---|
postgresql-18-pg-background ↗ 2.0.3-1.pgdg12+3 | PostgreSQL | No ↗ |
No packages match these filters. Try a different name or license, or clear the filters.
Dependencies
Packages shipped in this image, including the extension itself.
1 packages · Scanned
| Package / installed version | License evidence | Advisories |
|---|---|---|
postgresql-18-pg-background ↗ 2.0.3-1.pgdg12+3 | PostgreSQL | No ↗ |
No packages match these filters. Try a different name or license, or clear the filters.
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-pg-background/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: pg_background
Source: https://github.com/vibhorkum/pg_background
Files: *
Copyright: 1996-2026, PostgreSQL Global Development Group
2014-2026, Vibhor Kumar and contributors
License: postgresql
Comment: Copyight/License updated upstream in https://github.com/vibhorkum/pg_background/commit/ed1f6316
License: postgresql
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement is
hereby granted, provided that the above copyright notice and this paragraph
and the following two paragraphs appear in all copies.
.
IN NO EVENT SHALL THE AUTHORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING
OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHORS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.
THE AUTHORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE
AUTHORS HAVE NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.
SHA256: d6c4659ac255175f5c49eebf7aa1a242c272cb5e2830b5fb8a9d4ab3ef8fe8fe
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-pg-background/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: pg_background
Source: https://github.com/vibhorkum/pg_background
Files: *
Copyright: 1996-2026, PostgreSQL Global Development Group
2014-2026, Vibhor Kumar and contributors
License: postgresql
Comment: Copyight/License updated upstream in https://github.com/vibhorkum/pg_background/commit/ed1f6316
License: postgresql
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement is
hereby granted, provided that the above copyright notice and this paragraph
and the following two paragraphs appear in all copies.
.
IN NO EVENT SHALL THE AUTHORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING
OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHORS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.
THE AUTHORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE
AUTHORS HAVE NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.
SHA256: d6c4659ac255175f5c49eebf7aa1a242c272cb5e2830b5fb8a9d4ab3ef8fe8fe
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-pg-background/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: pg_background
Source: https://github.com/vibhorkum/pg_background
Files: *
Copyright: 1996-2026, PostgreSQL Global Development Group
2014-2026, Vibhor Kumar and contributors
License: postgresql
Comment: Copyight/License updated upstream in https://github.com/vibhorkum/pg_background/commit/ed1f6316
License: postgresql
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement is
hereby granted, provided that the above copyright notice and this paragraph
and the following two paragraphs appear in all copies.
.
IN NO EVENT SHALL THE AUTHORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING
OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHORS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.
THE AUTHORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE
AUTHORS HAVE NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.
SHA256: d6c4659ac255175f5c49eebf7aa1a242c272cb5e2830b5fb8a9d4ab3ef8fe8fe
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-pg-background/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: pg_background
Source: https://github.com/vibhorkum/pg_background
Files: *
Copyright: 1996-2026, PostgreSQL Global Development Group
2014-2026, Vibhor Kumar and contributors
License: postgresql
Comment: Copyight/License updated upstream in https://github.com/vibhorkum/pg_background/commit/ed1f6316
License: postgresql
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement is
hereby granted, provided that the above copyright notice and this paragraph
and the following two paragraphs appear in all copies.
.
IN NO EVENT SHALL THE AUTHORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING
OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHORS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.
THE AUTHORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE
AUTHORS HAVE NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.
SHA256: d6c4659ac255175f5c49eebf7aa1a242c272cb5e2830b5fb8a9d4ab3ef8fe8fe
Versions
Extension versions and the images built from them.
Tagged GHCR builds fetched .
