← Browse the extensions catalog

powa

Source README ↗

Overview

PostgreSQL Workload Analyzer server-side history and snapshot schema. Upstream project .

Package details

Extension version
5.3.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
pg_stat_statements (from the PostgreSQL base image)
btree_gist (from the PostgreSQL base image)
SQL installation
CREATE EXTENSION powa;
SQL version
5.3.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_stat_statements,powa'

These recipe settings are used in automated smoke tests.

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.

View information about checks. Automated results are informational only; some categories may not apply to this project.

Scanned · Download cached scan ↓

Dangerous-Workflow10

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

Reasoning: no dangerous workflow patterns detected

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

Branch-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-Review0

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

Reasoning: Found 2/30 approved changesets -- score normalized to 0

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

Maintained1

Determines if the project is "actively maintained".

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

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/powa_archivist.yml:1
  • Warn: no topLevel permission defined: .github/workflows/powa_archivist_git.yml:1
  • Warn: no topLevel permission defined: .github/workflows/tests.yml:1
  • Info: no jobLevel write permissions found

Check details ↗

Vulnerabilities10

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 0 existing vulnerabilities detected

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/tests.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/powa-team/powa-archivist/tests.yml/master?enable=pin
  • Info: 0 out of 1 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 30 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 ↗

CI-Tests6

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

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

Check details ↗

CII-Best-Practices0

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

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

Check details ↗

Contributors10

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

Reasoning: project has 15 contributing companies or organizations

  • Info: found contributions from: Debian, HypoPG, OPMDG, aiven, asp, cybertec-postgresql, dalibo, debian, niledatabase, oftc, pgmag, postgresqlfr, powa-team, replicase, scrive

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.md:0
  • Info: FSF or OSI recognized license: PostgreSQL License: LICENSE.md:0

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • LicenseRef-da6ebe447e7f55e3528039ef80259abcbe1d0ac4cd52b90d720f7738043a2a851 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

PostgreSQL Workload Analyzer server-side history and snapshot schema. Upstream project .

Package details

Extension version
5.3.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
pg_stat_statements (from the PostgreSQL base image)
btree_gist (from the PostgreSQL base image)
SQL installation
CREATE EXTENSION powa;
SQL version
5.3.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_stat_statements,powa'

These recipe settings are used in automated smoke tests.

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.

View information about checks. Automated results are informational only; some categories may not apply to this project.

Scanned · Download cached scan ↓

Dangerous-Workflow10

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

Reasoning: no dangerous workflow patterns detected

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

Branch-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-Review0

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

Reasoning: Found 2/30 approved changesets -- score normalized to 0

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

Maintained1

Determines if the project is "actively maintained".

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

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/powa_archivist.yml:1
  • Warn: no topLevel permission defined: .github/workflows/powa_archivist_git.yml:1
  • Warn: no topLevel permission defined: .github/workflows/tests.yml:1
  • Info: no jobLevel write permissions found

Check details ↗

Vulnerabilities10

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 0 existing vulnerabilities detected

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/tests.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/powa-team/powa-archivist/tests.yml/master?enable=pin
  • Info: 0 out of 1 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 30 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 ↗

CI-Tests6

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

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

Check details ↗

CII-Best-Practices0

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

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

Check details ↗

Contributors10

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

Reasoning: project has 15 contributing companies or organizations

  • Info: found contributions from: Debian, HypoPG, OPMDG, aiven, asp, cybertec-postgresql, dalibo, debian, niledatabase, oftc, pgmag, postgresqlfr, powa-team, replicase, scrive

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.md:0
  • Info: FSF or OSI recognized license: PostgreSQL License: LICENSE.md:0

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • LicenseRef-da6ebe447e7f55e3528039ef80259abcbe1d0ac4cd52b90d720f7738043a2a851 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

PostgreSQL Workload Analyzer server-side history and snapshot schema. Upstream project .

Package details

Extension version
5.3.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
pg_stat_statements (from the PostgreSQL base image)
btree_gist (from the PostgreSQL base image)
SQL installation
CREATE EXTENSION powa;
SQL version
5.3.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_stat_statements,powa'

These recipe settings are used in automated smoke tests.

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.

View information about checks. Automated results are informational only; some categories may not apply to this project.

Scanned · Download cached scan ↓

Dangerous-Workflow10

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

Reasoning: no dangerous workflow patterns detected

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

Branch-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-Review0

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

Reasoning: Found 2/30 approved changesets -- score normalized to 0

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

Maintained1

Determines if the project is "actively maintained".

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

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/powa_archivist.yml:1
  • Warn: no topLevel permission defined: .github/workflows/powa_archivist_git.yml:1
  • Warn: no topLevel permission defined: .github/workflows/tests.yml:1
  • Info: no jobLevel write permissions found

Check details ↗

Vulnerabilities10

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 0 existing vulnerabilities detected

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/tests.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/powa-team/powa-archivist/tests.yml/master?enable=pin
  • Info: 0 out of 1 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 30 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 ↗

CI-Tests6

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

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

Check details ↗

CII-Best-Practices0

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

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

Check details ↗

Contributors10

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

Reasoning: project has 15 contributing companies or organizations

  • Info: found contributions from: Debian, HypoPG, OPMDG, aiven, asp, cybertec-postgresql, dalibo, debian, niledatabase, oftc, pgmag, postgresqlfr, powa-team, replicase, scrive

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.md:0
  • Info: FSF or OSI recognized license: PostgreSQL License: LICENSE.md:0

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • LicenseRef-da6ebe447e7f55e3528039ef80259abcbe1d0ac4cd52b90d720f7738043a2a851 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

PostgreSQL Workload Analyzer server-side history and snapshot schema. Upstream project .

Package details

Extension version
5.3.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
pg_stat_statements (from the PostgreSQL base image)
btree_gist (from the PostgreSQL base image)
SQL installation
CREATE EXTENSION powa;
SQL version
5.3.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_stat_statements,powa'

These recipe settings are used in automated smoke tests.

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.

View information about checks. Automated results are informational only; some categories may not apply to this project.

Scanned · Download cached scan ↓

Dangerous-Workflow10

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

Reasoning: no dangerous workflow patterns detected

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

Branch-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-Review0

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

Reasoning: Found 2/30 approved changesets -- score normalized to 0

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

Maintained1

Determines if the project is "actively maintained".

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

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/powa_archivist.yml:1
  • Warn: no topLevel permission defined: .github/workflows/powa_archivist_git.yml:1
  • Warn: no topLevel permission defined: .github/workflows/tests.yml:1
  • Info: no jobLevel write permissions found

Check details ↗

Vulnerabilities10

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 0 existing vulnerabilities detected

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/tests.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/powa-team/powa-archivist/tests.yml/master?enable=pin
  • Info: 0 out of 1 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 30 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 ↗

CI-Tests6

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

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

Check details ↗

CII-Best-Practices0

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

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

Check details ↗

Contributors10

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

Reasoning: project has 15 contributing companies or organizations

  • Info: found contributions from: Debian, HypoPG, OPMDG, aiven, asp, cybertec-postgresql, dalibo, debian, niledatabase, oftc, pgmag, postgresqlfr, powa-team, replicase, scrive

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.md:0
  • Info: FSF or OSI recognized license: PostgreSQL License: LICENSE.md:0

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • LicenseRef-da6ebe447e7f55e3528039ef80259abcbe1d0ac4cd52b90d720f7738043a2a851 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