← Browse the extensions catalog

pg-permissions

Source README ↗

Overview

see all permissions in a PostgreSQL database. Upstream documentation .

Package details

Extension version
1.4.1
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_permissions;
SQL version
1.4 — differs from extension version 1.4.1

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 '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-Review1

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

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

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: 2 commit(s) and 0 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/regression.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/regression.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_permissions/regression.yml/master?enable=pin
  • Warn: containerImage not pinned by hash: test/Dockerfile:9: pin your Docker image by updating debian:bookworm-slim to debian:bookworm-slim@sha256:734a72b3d6142a71993b4bc580ca01d8ca687f77a2c422d96a961d3376b179bc
  • Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 1 containerImage 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 ↗

CI-Tests5

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

Reasoning: 2 out of 4 merged PRs checked by a CI test -- score normalized to 5

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 ↗

Contributors6

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

Reasoning: project has 2 contributing companies or organizations -- score normalized to 6

  • Info: found contributions from: cybertec, cybertec postgresql international gmbh

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE: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

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

see all permissions in a PostgreSQL database. Upstream documentation .

Package details

Extension version
1.4.1
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_permissions;
SQL version
1.4 — differs from extension version 1.4.1

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 '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-Review1

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

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

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: 2 commit(s) and 0 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/regression.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/regression.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_permissions/regression.yml/master?enable=pin
  • Warn: containerImage not pinned by hash: test/Dockerfile:9: pin your Docker image by updating debian:bookworm-slim to debian:bookworm-slim@sha256:734a72b3d6142a71993b4bc580ca01d8ca687f77a2c422d96a961d3376b179bc
  • Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 1 containerImage 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 ↗

CI-Tests5

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

Reasoning: 2 out of 4 merged PRs checked by a CI test -- score normalized to 5

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 ↗

Contributors6

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

Reasoning: project has 2 contributing companies or organizations -- score normalized to 6

  • Info: found contributions from: cybertec, cybertec postgresql international gmbh

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE: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

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

see all permissions in a PostgreSQL database. Upstream documentation .

Package details

Extension version
1.4.1
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_permissions;
SQL version
1.4 — differs from extension version 1.4.1

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 '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-Review1

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

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

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: 2 commit(s) and 0 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/regression.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/regression.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_permissions/regression.yml/master?enable=pin
  • Warn: containerImage not pinned by hash: test/Dockerfile:9: pin your Docker image by updating debian:bookworm-slim to debian:bookworm-slim@sha256:734a72b3d6142a71993b4bc580ca01d8ca687f77a2c422d96a961d3376b179bc
  • Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 1 containerImage 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 ↗

CI-Tests5

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

Reasoning: 2 out of 4 merged PRs checked by a CI test -- score normalized to 5

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 ↗

Contributors6

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

Reasoning: project has 2 contributing companies or organizations -- score normalized to 6

  • Info: found contributions from: cybertec, cybertec postgresql international gmbh

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE: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

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

see all permissions in a PostgreSQL database. Upstream documentation .

Package details

Extension version
1.4.1
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_permissions;
SQL version
1.4 — differs from extension version 1.4.1

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 '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-Review1

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

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

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: 2 commit(s) and 0 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/regression.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/regression.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_permissions/regression.yml/master?enable=pin
  • Warn: containerImage not pinned by hash: test/Dockerfile:9: pin your Docker image by updating debian:bookworm-slim to debian:bookworm-slim@sha256:734a72b3d6142a71993b4bc580ca01d8ca687f77a2c422d96a961d3376b179bc
  • Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 1 containerImage 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 ↗

CI-Tests5

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

Reasoning: 2 out of 4 merged PRs checked by a CI test -- score normalized to 5

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 ↗

Contributors6

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

Reasoning: project has 2 contributing companies or organizations -- score normalized to 6

  • Info: found contributions from: cybertec, cybertec postgresql international gmbh

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE: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

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