← Browse the extensions catalog

pg-pwhash

Source README ↗

Overview

pg_pwhash provides adaptive Argon2, scrypt, and yescrypt password-hashing functions backed by packaged cryptographic libraries. See the upstream project for the extension documentation.

Package details

Extension version
1.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_pwhash;
SQL version
1.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 · 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-Protection5

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 'main'
  • Info: 'force pushes' disabled on branch 'main'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'main'
  • Info: 'stale review dismissal' is required to merge on branch 'main'
  • Warn: required approving review count is 1 on branch 'main'
  • Warn: codeowners review is not required on branch 'main'
  • Warn: 'last push approval' is disabled on branch 'main'
  • Warn: no status checks found to merge onto branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review0

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

Reasoning: Found 0/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 ↗

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/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:43: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_pwhash/tests.yml/main?enable=pin
  • Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned

Check details ↗

SAST0

Determines if the project uses static code analysis.

Reasoning: no SAST tool detected

  • Warn: no pull requests merged into dev branch

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

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

Reasoning: no pull request found

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 6 contributing companies or organizations

  • Info: found contributions from: Debian, cybertec postgresql international gmbh, cybertec-postgresql, debian, oftc, powa-team

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE:0
  • Info: FSF or OSI recognized license: MIT License: LICENSE:0

Check details ↗

Extension recipe
MIT

License expressions in the shipped package inventory

  • Apache-2.0 AND LicenseRef-CC01 package
  • BSD-2-Clause AND GPL-2.0-only AND GPL-2.0-or-later AND ISC1 package
  • LicenseRef-Expat1 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 →

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

Evidence

Overview

pg_pwhash provides adaptive Argon2, scrypt, and yescrypt password-hashing functions backed by packaged cryptographic libraries. See the upstream project for the extension documentation.

Package details

Extension version
1.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_pwhash;
SQL version
1.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 · 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-Protection5

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 'main'
  • Info: 'force pushes' disabled on branch 'main'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'main'
  • Info: 'stale review dismissal' is required to merge on branch 'main'
  • Warn: required approving review count is 1 on branch 'main'
  • Warn: codeowners review is not required on branch 'main'
  • Warn: 'last push approval' is disabled on branch 'main'
  • Warn: no status checks found to merge onto branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review0

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

Reasoning: Found 0/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 ↗

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/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:43: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_pwhash/tests.yml/main?enable=pin
  • Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned

Check details ↗

SAST0

Determines if the project uses static code analysis.

Reasoning: no SAST tool detected

  • Warn: no pull requests merged into dev branch

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

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

Reasoning: no pull request found

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 6 contributing companies or organizations

  • Info: found contributions from: Debian, cybertec postgresql international gmbh, cybertec-postgresql, debian, oftc, powa-team

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE:0
  • Info: FSF or OSI recognized license: MIT License: LICENSE:0

Check details ↗

Extension recipe
MIT

License expressions in the shipped package inventory

  • Apache-2.0 AND LicenseRef-CC01 package
  • BSD-2-Clause AND GPL-2.0-only AND GPL-2.0-or-later AND ISC1 package
  • LicenseRef-Expat1 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 →

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

Evidence

Overview

pg_pwhash provides adaptive Argon2, scrypt, and yescrypt password-hashing functions backed by packaged cryptographic libraries. See the upstream project for the extension documentation.

Package details

Extension version
1.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_pwhash;
SQL version
1.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 · 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-Protection5

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 'main'
  • Info: 'force pushes' disabled on branch 'main'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'main'
  • Info: 'stale review dismissal' is required to merge on branch 'main'
  • Warn: required approving review count is 1 on branch 'main'
  • Warn: codeowners review is not required on branch 'main'
  • Warn: 'last push approval' is disabled on branch 'main'
  • Warn: no status checks found to merge onto branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review0

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

Reasoning: Found 0/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 ↗

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/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:43: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_pwhash/tests.yml/main?enable=pin
  • Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned

Check details ↗

SAST0

Determines if the project uses static code analysis.

Reasoning: no SAST tool detected

  • Warn: no pull requests merged into dev branch

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

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

Reasoning: no pull request found

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 6 contributing companies or organizations

  • Info: found contributions from: Debian, cybertec postgresql international gmbh, cybertec-postgresql, debian, oftc, powa-team

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE:0
  • Info: FSF or OSI recognized license: MIT License: LICENSE:0

Check details ↗

Extension recipe
MIT

License expressions in the shipped package inventory

  • BSD-2-Clause AND GPL-2.0-only AND GPL-2.0-or-later AND ISC1 package
  • LicenseRef-Expat1 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 →

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

Evidence

Overview

pg_pwhash provides adaptive Argon2, scrypt, and yescrypt password-hashing functions backed by packaged cryptographic libraries. See the upstream project for the extension documentation.

Package details

Extension version
1.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_pwhash;
SQL version
1.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 · 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-Protection5

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 'main'
  • Info: 'force pushes' disabled on branch 'main'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'main'
  • Info: 'stale review dismissal' is required to merge on branch 'main'
  • Warn: required approving review count is 1 on branch 'main'
  • Warn: codeowners review is not required on branch 'main'
  • Warn: 'last push approval' is disabled on branch 'main'
  • Warn: no status checks found to merge onto branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review0

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

Reasoning: Found 0/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 ↗

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/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:43: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_pwhash/tests.yml/main?enable=pin
  • Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned

Check details ↗

SAST0

Determines if the project uses static code analysis.

Reasoning: no SAST tool detected

  • Warn: no pull requests merged into dev branch

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

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

Reasoning: no pull request found

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 6 contributing companies or organizations

  • Info: found contributions from: Debian, cybertec postgresql international gmbh, cybertec-postgresql, debian, oftc, powa-team

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE:0
  • Info: FSF or OSI recognized license: MIT License: LICENSE:0

Check details ↗

Extension recipe
MIT

License expressions in the shipped package inventory

  • BSD-2-Clause AND GPL-2.0-only AND GPL-2.0-or-later AND ISC1 package
  • LicenseRef-Expat1 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 →

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

Evidence