← Browse the extensions catalog

pg-partman

Source README ↗

Overview

pg_partman creates and maintains time-based and ID-based PostgreSQL partition sets. Its optional background worker can run partition maintenance automatically.

Package details

Extension version
5.5.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 pg_partman;
SQL version
5.5.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_partman_bgw'

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

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

Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md

Check details ↗

Code-Review4

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

Reasoning: Found 12/28 approved changesets -- score normalized to 4

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 3 commit(s) and 12 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

  • 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:18: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/ci.yml/development?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/release.yml/development?enable=pin
  • Info: 0 out of 2 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 17 are checked with a SAST tool

Check details ↗

Security-Policy4

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Warn: no linked content found
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

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

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • 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_partman creates and maintains time-based and ID-based PostgreSQL partition sets. Its optional background worker can run partition maintenance automatically.

Package details

Extension version
5.5.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 pg_partman;
SQL version
5.5.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_partman_bgw'

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

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

Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md

Check details ↗

Code-Review4

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

Reasoning: Found 12/28 approved changesets -- score normalized to 4

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 3 commit(s) and 12 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

  • 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:18: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/ci.yml/development?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/release.yml/development?enable=pin
  • Info: 0 out of 2 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 17 are checked with a SAST tool

Check details ↗

Security-Policy4

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Warn: no linked content found
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

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

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • 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_partman creates and maintains time-based and ID-based PostgreSQL partition sets. Its optional background worker can run partition maintenance automatically.

Package details

Extension version
5.5.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 pg_partman;
SQL version
5.5.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_partman_bgw'

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

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

Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md

Check details ↗

Code-Review4

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

Reasoning: Found 12/28 approved changesets -- score normalized to 4

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 3 commit(s) and 12 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

  • 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:18: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/ci.yml/development?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/release.yml/development?enable=pin
  • Info: 0 out of 2 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 17 are checked with a SAST tool

Check details ↗

Security-Policy4

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Warn: no linked content found
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

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

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • 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_partman creates and maintains time-based and ID-based PostgreSQL partition sets. Its optional background worker can run partition maintenance automatically.

Package details

Extension version
5.5.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 pg_partman;
SQL version
5.5.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_partman_bgw'

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

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

Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md

Check details ↗

Code-Review4

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

Reasoning: Found 12/28 approved changesets -- score normalized to 4

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 3 commit(s) and 12 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

  • 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:18: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/ci.yml/development?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/release.yml/development?enable=pin
  • Info: 0 out of 2 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 17 are checked with a SAST tool

Check details ↗

Security-Policy4

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Warn: no linked content found
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

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

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • 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