← Browse the extensions catalog

pg-background

Source README ↗

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

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

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

Check details ↗

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

Check details ↗

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

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

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

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

Check details ↗

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

Check details ↗

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

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 ↗

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
PostgreSQL

License expressions in the shipped package inventory

  • PostgreSQL1 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 →

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

Evidence

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

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

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

Check details ↗

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

Check details ↗

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

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

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

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

Check details ↗

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

Check details ↗

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

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 ↗

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
PostgreSQL

License expressions in the shipped package inventory

  • PostgreSQL1 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 →

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

Evidence

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

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

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

Check details ↗

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

Check details ↗

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

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

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

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

Check details ↗

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

Check details ↗

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

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 ↗

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
PostgreSQL

License expressions in the shipped package inventory

  • PostgreSQL1 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 →

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

Evidence

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

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

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

Check details ↗

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

Check details ↗

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

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

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

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

Check details ↗

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

Check details ↗

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

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 ↗

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
PostgreSQL

License expressions in the shipped package inventory

  • PostgreSQL1 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 →

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

Evidence