← Browse the extensions catalog

plproxy

Source README ↗

Overview

database partitioning system for PostgreSQL 18. Upstream documentation .

Package details

Extension version
2.12.0
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 plproxy;
SQL version
2.12.0

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

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: branch protection is not maximal on development and all release branches

  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Warn: could not determine whether codeowners review is allowed
  • Warn: no status checks found to merge onto branch 'master'
  • Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings

Check details ↗

Code-Review0

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

Reasoning: Found 1/26 approved changesets -- score normalized to 0

Check details ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-Permissions0

Determines if the project's workflows follow the principle of least privilege.

Reasoning: detected GitHub workflow tokens with excessive permissions

  • Warn: no topLevel permission defined: .github/workflows/ci.yml:1
  • Warn: no topLevel permission defined: .github/workflows/release.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

  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:120: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:175: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
  • Info: 0 out of 5 GitHub-owned GitHubAction 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 6 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

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: COPYRIGHT:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
ISC

License expressions in the shipped package inventory

  • ISC1 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

database partitioning system for PostgreSQL 18. Upstream documentation .

Package details

Extension version
2.12.0
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 plproxy;
SQL version
2.12.0

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

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: branch protection is not maximal on development and all release branches

  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Warn: could not determine whether codeowners review is allowed
  • Warn: no status checks found to merge onto branch 'master'
  • Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings

Check details ↗

Code-Review0

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

Reasoning: Found 1/26 approved changesets -- score normalized to 0

Check details ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-Permissions0

Determines if the project's workflows follow the principle of least privilege.

Reasoning: detected GitHub workflow tokens with excessive permissions

  • Warn: no topLevel permission defined: .github/workflows/ci.yml:1
  • Warn: no topLevel permission defined: .github/workflows/release.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

  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:120: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:175: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
  • Info: 0 out of 5 GitHub-owned GitHubAction 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 6 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

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: COPYRIGHT:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
ISC

License expressions in the shipped package inventory

  • ISC1 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

database partitioning system for PostgreSQL 18. Upstream documentation .

Package details

Extension version
2.12.0
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 plproxy;
SQL version
2.12.0

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

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: branch protection is not maximal on development and all release branches

  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Warn: could not determine whether codeowners review is allowed
  • Warn: no status checks found to merge onto branch 'master'
  • Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings

Check details ↗

Code-Review0

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

Reasoning: Found 1/26 approved changesets -- score normalized to 0

Check details ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-Permissions0

Determines if the project's workflows follow the principle of least privilege.

Reasoning: detected GitHub workflow tokens with excessive permissions

  • Warn: no topLevel permission defined: .github/workflows/ci.yml:1
  • Warn: no topLevel permission defined: .github/workflows/release.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

  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:120: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:175: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
  • Info: 0 out of 5 GitHub-owned GitHubAction 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 6 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

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: COPYRIGHT:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
ISC

License expressions in the shipped package inventory

  • ISC1 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

database partitioning system for PostgreSQL 18. Upstream documentation .

Package details

Extension version
2.12.0
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 plproxy;
SQL version
2.12.0

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

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: branch protection is not maximal on development and all release branches

  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Warn: could not determine whether codeowners review is allowed
  • Warn: no status checks found to merge onto branch 'master'
  • Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings

Check details ↗

Code-Review0

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

Reasoning: Found 1/26 approved changesets -- score normalized to 0

Check details ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-Permissions0

Determines if the project's workflows follow the principle of least privilege.

Reasoning: detected GitHub workflow tokens with excessive permissions

  • Warn: no topLevel permission defined: .github/workflows/ci.yml:1
  • Warn: no topLevel permission defined: .github/workflows/release.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

  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:120: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:175: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
  • Info: 0 out of 5 GitHub-owned GitHubAction 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 6 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

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: COPYRIGHT:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
ISC

License expressions in the shipped package inventory

  • ISC1 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