← Browse the extensions catalog

pg-crash

Source README ↗

Overview

pg_crash is a PostgreSQL extension designed for fault injection and chaos engineering . It allows administrators to simulate various failure scenarios—such as backend crashes and signal handling issues—to verify the resilience of High Availability (HA) clusters and self-healing mechanisms.

Package details

Extension version
0.3
Image built
Publisher
cloudnative-pg
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
This recipe does not use CREATE EXTENSION.
SQL version
Not recorded

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_crash'

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

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

Reasoning: no workflows found

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 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Info: 'stale review dismissal' is required to merge on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Warn: codeowners review is not required on branch 'master'
  • Warn: 'last push approval' is disabled 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-Review0

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

Reasoning: Found 1/21 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-PermissionsUnknown

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

Reasoning: No tokens 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-DependenciesUnknown

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: no dependencies found

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 2 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-Tests0

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

Reasoning: 0 out of 1 merged PRs checked by a CI test -- score normalized to 0

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, debian, freelance postgresql engineer / consultant, 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: BSD 3-Clause "New" or "Revised" License: LICENSE:0

Check details ↗

Extension recipe
BSD-3-Clause

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

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

Unavailable

Overview

pg_crash is a PostgreSQL extension designed for fault injection and chaos engineering . It allows administrators to simulate various failure scenarios—such as backend crashes and signal handling issues—to verify the resilience of High Availability (HA) clusters and self-healing mechanisms.

Package details

Extension version
0.3
Image built
Publisher
cloudnative-pg
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
This recipe does not use CREATE EXTENSION.
SQL version
Not recorded

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_crash'

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

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

Reasoning: no workflows found

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 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Info: 'stale review dismissal' is required to merge on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Warn: codeowners review is not required on branch 'master'
  • Warn: 'last push approval' is disabled 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-Review0

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

Reasoning: Found 1/21 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-PermissionsUnknown

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

Reasoning: No tokens 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-DependenciesUnknown

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: no dependencies found

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 2 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-Tests0

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

Reasoning: 0 out of 1 merged PRs checked by a CI test -- score normalized to 0

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, debian, freelance postgresql engineer / consultant, 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: BSD 3-Clause "New" or "Revised" License: LICENSE:0

Check details ↗

Extension recipe
BSD-3-Clause

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

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

Unavailable

Overview

pg_crash is a PostgreSQL extension designed for fault injection and chaos engineering . It allows administrators to simulate various failure scenarios—such as backend crashes and signal handling issues—to verify the resilience of High Availability (HA) clusters and self-healing mechanisms.

Package details

Extension version
0.3
Image built
Publisher
cloudnative-pg
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
This recipe does not use CREATE EXTENSION.
SQL version
Not recorded

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_crash'

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

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

Reasoning: no workflows found

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 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Info: 'stale review dismissal' is required to merge on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Warn: codeowners review is not required on branch 'master'
  • Warn: 'last push approval' is disabled 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-Review0

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

Reasoning: Found 1/21 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-PermissionsUnknown

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

Reasoning: No tokens 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-DependenciesUnknown

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: no dependencies found

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 2 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-Tests0

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

Reasoning: 0 out of 1 merged PRs checked by a CI test -- score normalized to 0

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, debian, freelance postgresql engineer / consultant, 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: BSD 3-Clause "New" or "Revised" License: LICENSE:0

Check details ↗

Extension recipe
BSD-3-Clause

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

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

Unavailable

Overview

pg_crash is a PostgreSQL extension designed for fault injection and chaos engineering . It allows administrators to simulate various failure scenarios—such as backend crashes and signal handling issues—to verify the resilience of High Availability (HA) clusters and self-healing mechanisms.

Package details

Extension version
0.3
Image built
Publisher
cloudnative-pg
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
This recipe does not use CREATE EXTENSION.
SQL version
Not recorded

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_crash'

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

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

Reasoning: no workflows found

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 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Info: 'stale review dismissal' is required to merge on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Warn: codeowners review is not required on branch 'master'
  • Warn: 'last push approval' is disabled 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-Review0

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

Reasoning: Found 1/21 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-PermissionsUnknown

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

Reasoning: No tokens 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-DependenciesUnknown

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: no dependencies found

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 2 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-Tests0

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

Reasoning: 0 out of 1 merged PRs checked by a CI test -- score normalized to 0

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, debian, freelance postgresql engineer / consultant, 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: BSD 3-Clause "New" or "Revised" License: LICENSE:0

Check details ↗

Extension recipe
BSD-3-Clause

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

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

Unavailable