← Browse the extensions catalog

pg-duckdb

Source README ↗

Overview

pg_duckdb integrates DuckDB's analytical query engine with PostgreSQL. It supports analytical queries over PostgreSQL tables and external data. This image supports PostgreSQL 18 on Debian Bookworm and Trixie for AMD64 and ARM64.

Package details

Extension version
1.2.0
Image built
Publisher
cnpg-extensions
Build
Universe
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_duckdb;
SQL version
1.2.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_duckdb'

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

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

Reasoning: dangerous workflow patterns detected

  • Warn: script injection with untrusted input ' github.head_ref || github.ref_name ': .github/workflows/docker.yaml:55

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

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'main'
  • Info: 'stale review dismissal' is required to merge on branch 'main'
  • Warn: branch 'main' does not require approvers
  • Warn: codeowners review is not required on branch 'main'
  • Warn: 'last push approval' is disabled on branch 'main'
  • Warn: 'up-to-date branches' is disabled on branch 'main'
  • Info: status check found to merge onto on branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review1

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

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

Maintained10

Determines if the project is "actively maintained".

Reasoning: 30 commit(s) and 9 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: jobLevel 'contents' permission set to 'write': .github/workflows/release_static.yaml:229
  • Warn: no topLevel permission defined: .github/workflows/build_and_test.yaml:1
  • Warn: topLevel 'contents' permission set to 'write': .github/workflows/docker.yaml:5
  • Warn: no topLevel permission defined: .github/workflows/release_static.yaml:1

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: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:73: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:79: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:87: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:115: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:130: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:220: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:226: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:251: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:268: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:326: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:112: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/docker.yaml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:83: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:88: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:55: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:124: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:131: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:212: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:246: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: containerImage not pinned by hash: Dockerfile:1
  • Warn: containerImage not pinned by hash: Dockerfile:6
  • Warn: containerImage not pinned by hash: Dockerfile:54
  • Warn: containerImage not pinned by hash: Dockerfile:63
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:25
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:137
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:275
  • Info: 0 out of 16 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 7 third-party GitHubAction dependencies pinned
  • Info: 0 out of 4 containerImage dependencies pinned
  • Info: 0 out of 3 pipCommand 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-Tests9

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

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

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

  • Info: found contributions from: amazon web services, apache, duckdb, duckdblabs, motherduck, motherduckdb, opensource4you, pgbouncer, postgres professional

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

  • LicenseRef-Notices-24a64e5bb83d0960d18356961 package
  • LicenseRef-Notices-351f3d33433a8db877ebe1a81 package
  • LicenseRef-Notices-4e3e0f5d65e12c926bd342d61 package
  • LicenseRef-Notices-57a1b805e32237caa68e47071 package
  • LicenseRef-Notices-6e3b7206a2a68d959274c2891 package
  • LicenseRef-Notices-947619133335f488ba88fad71 package
  • LicenseRef-Notices-cfb8982ca97787da03dba5861 package
  • LicenseRef-Notices-d012a4200bdc82a92471f9e41 package
1 more license expressions
  • LicenseRef-Notices-d8f1a1e28205909187a6d6871 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 →

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

Evidence

Overview

pg_duckdb integrates DuckDB's analytical query engine with PostgreSQL. It supports analytical queries over PostgreSQL tables and external data. This image supports PostgreSQL 18 on Debian Bookworm and Trixie for AMD64 and ARM64.

Package details

Extension version
1.2.0
Image built
Publisher
cnpg-extensions
Build
Universe
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_duckdb;
SQL version
1.2.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_duckdb'

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

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

Reasoning: dangerous workflow patterns detected

  • Warn: script injection with untrusted input ' github.head_ref || github.ref_name ': .github/workflows/docker.yaml:55

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

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'main'
  • Info: 'stale review dismissal' is required to merge on branch 'main'
  • Warn: branch 'main' does not require approvers
  • Warn: codeowners review is not required on branch 'main'
  • Warn: 'last push approval' is disabled on branch 'main'
  • Warn: 'up-to-date branches' is disabled on branch 'main'
  • Info: status check found to merge onto on branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review1

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

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

Maintained10

Determines if the project is "actively maintained".

Reasoning: 30 commit(s) and 9 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: jobLevel 'contents' permission set to 'write': .github/workflows/release_static.yaml:229
  • Warn: no topLevel permission defined: .github/workflows/build_and_test.yaml:1
  • Warn: topLevel 'contents' permission set to 'write': .github/workflows/docker.yaml:5
  • Warn: no topLevel permission defined: .github/workflows/release_static.yaml:1

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: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:73: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:79: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:87: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:115: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:130: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:220: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:226: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:251: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:268: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:326: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:112: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/docker.yaml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:83: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:88: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:55: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:124: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:131: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:212: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:246: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: containerImage not pinned by hash: Dockerfile:1
  • Warn: containerImage not pinned by hash: Dockerfile:6
  • Warn: containerImage not pinned by hash: Dockerfile:54
  • Warn: containerImage not pinned by hash: Dockerfile:63
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:25
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:137
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:275
  • Info: 0 out of 16 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 7 third-party GitHubAction dependencies pinned
  • Info: 0 out of 4 containerImage dependencies pinned
  • Info: 0 out of 3 pipCommand 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-Tests9

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

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

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

  • Info: found contributions from: amazon web services, apache, duckdb, duckdblabs, motherduck, motherduckdb, opensource4you, pgbouncer, postgres professional

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

  • LicenseRef-Notices-24a64e5bb83d0960d18356961 package
  • LicenseRef-Notices-351f3d33433a8db877ebe1a81 package
  • LicenseRef-Notices-4e3e0f5d65e12c926bd342d61 package
  • LicenseRef-Notices-57a1b805e32237caa68e47071 package
  • LicenseRef-Notices-6e3b7206a2a68d959274c2891 package
  • LicenseRef-Notices-947619133335f488ba88fad71 package
  • LicenseRef-Notices-cfb8982ca97787da03dba5861 package
  • LicenseRef-Notices-d012a4200bdc82a92471f9e41 package
1 more license expressions
  • LicenseRef-Notices-d8f1a1e28205909187a6d6871 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 →

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

Evidence

Overview

pg_duckdb integrates DuckDB's analytical query engine with PostgreSQL. It supports analytical queries over PostgreSQL tables and external data. This image supports PostgreSQL 18 on Debian Bookworm and Trixie for AMD64 and ARM64.

Package details

Extension version
1.2.0
Image built
Publisher
cnpg-extensions
Build
Universe
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_duckdb;
SQL version
1.2.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_duckdb'

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

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

Reasoning: dangerous workflow patterns detected

  • Warn: script injection with untrusted input ' github.head_ref || github.ref_name ': .github/workflows/docker.yaml:55

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

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'main'
  • Info: 'stale review dismissal' is required to merge on branch 'main'
  • Warn: branch 'main' does not require approvers
  • Warn: codeowners review is not required on branch 'main'
  • Warn: 'last push approval' is disabled on branch 'main'
  • Warn: 'up-to-date branches' is disabled on branch 'main'
  • Info: status check found to merge onto on branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review1

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

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

Maintained10

Determines if the project is "actively maintained".

Reasoning: 30 commit(s) and 9 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: jobLevel 'contents' permission set to 'write': .github/workflows/release_static.yaml:229
  • Warn: no topLevel permission defined: .github/workflows/build_and_test.yaml:1
  • Warn: topLevel 'contents' permission set to 'write': .github/workflows/docker.yaml:5
  • Warn: no topLevel permission defined: .github/workflows/release_static.yaml:1

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: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:73: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:79: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:87: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:115: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:130: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:220: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:226: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:251: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:268: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:326: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:112: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/docker.yaml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:83: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:88: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:55: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:124: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:131: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:212: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:246: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: containerImage not pinned by hash: Dockerfile:1
  • Warn: containerImage not pinned by hash: Dockerfile:6
  • Warn: containerImage not pinned by hash: Dockerfile:54
  • Warn: containerImage not pinned by hash: Dockerfile:63
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:25
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:137
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:275
  • Info: 0 out of 16 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 7 third-party GitHubAction dependencies pinned
  • Info: 0 out of 4 containerImage dependencies pinned
  • Info: 0 out of 3 pipCommand 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-Tests9

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

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

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

  • Info: found contributions from: amazon web services, apache, duckdb, duckdblabs, motherduck, motherduckdb, opensource4you, pgbouncer, postgres professional

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

  • LicenseRef-Notices-24a64e5bb83d0960d18356961 package
  • LicenseRef-Notices-561435c945d1cdbb47d6dfcf1 package
  • LicenseRef-Notices-57a1b805e32237caa68e47071 package
  • LicenseRef-Notices-6e3b7206a2a68d959274c2891 package
  • LicenseRef-Notices-947619133335f488ba88fad71 package
  • LicenseRef-Notices-b19656e73364773fec988efe1 package
  • LicenseRef-Notices-c71237ee656b7028ab20f5921 package
  • LicenseRef-Notices-d1907587c823539bed1361211 package
1 more license expressions
  • LicenseRef-Notices-f5760bfd887ffc76b3654f6a1 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 →

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

Evidence

Overview

pg_duckdb integrates DuckDB's analytical query engine with PostgreSQL. It supports analytical queries over PostgreSQL tables and external data. This image supports PostgreSQL 18 on Debian Bookworm and Trixie for AMD64 and ARM64.

Package details

Extension version
1.2.0
Image built
Publisher
cnpg-extensions
Build
Universe
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_duckdb;
SQL version
1.2.0

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_duckdb'

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

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

Reasoning: dangerous workflow patterns detected

  • Warn: script injection with untrusted input ' github.head_ref || github.ref_name ': .github/workflows/docker.yaml:55

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

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'main'
  • Info: 'stale review dismissal' is required to merge on branch 'main'
  • Warn: branch 'main' does not require approvers
  • Warn: codeowners review is not required on branch 'main'
  • Warn: 'last push approval' is disabled on branch 'main'
  • Warn: 'up-to-date branches' is disabled on branch 'main'
  • Info: status check found to merge onto on branch 'main'
  • Info: PRs are required in order to make changes on branch 'main'

Check details ↗

Code-Review1

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

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

Maintained10

Determines if the project is "actively maintained".

Reasoning: 30 commit(s) and 9 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: jobLevel 'contents' permission set to 'write': .github/workflows/release_static.yaml:229
  • Warn: no topLevel permission defined: .github/workflows/build_and_test.yaml:1
  • Warn: topLevel 'contents' permission set to 'write': .github/workflows/docker.yaml:5
  • Warn: no topLevel permission defined: .github/workflows/release_static.yaml:1

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: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:73: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:79: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:87: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:115: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:130: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:220: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:226: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:251: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:268: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:326: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build_and_test.yaml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/build_and_test.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:112: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/docker.yaml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:83: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/docker.yaml:88: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/docker.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:55: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:124: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:131: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:212: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release_static.yaml:246: update your workflow using https://app.stepsecurity.io/secureworkflow/duckdb/pg_duckdb/release_static.yaml/main?enable=pin
  • Warn: containerImage not pinned by hash: Dockerfile:1
  • Warn: containerImage not pinned by hash: Dockerfile:6
  • Warn: containerImage not pinned by hash: Dockerfile:54
  • Warn: containerImage not pinned by hash: Dockerfile:63
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:25
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:137
  • Warn: pipCommand not pinned by hash: .github/workflows/build_and_test.yaml:275
  • Info: 0 out of 16 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 7 third-party GitHubAction dependencies pinned
  • Info: 0 out of 4 containerImage dependencies pinned
  • Info: 0 out of 3 pipCommand 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-Tests9

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

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

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

  • Info: found contributions from: amazon web services, apache, duckdb, duckdblabs, motherduck, motherduckdb, opensource4you, pgbouncer, postgres professional

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

  • LicenseRef-Notices-24a64e5bb83d0960d18356961 package
  • LicenseRef-Notices-561435c945d1cdbb47d6dfcf1 package
  • LicenseRef-Notices-57a1b805e32237caa68e47071 package
  • LicenseRef-Notices-6e3b7206a2a68d959274c2891 package
  • LicenseRef-Notices-947619133335f488ba88fad71 package
  • LicenseRef-Notices-b19656e73364773fec988efe1 package
  • LicenseRef-Notices-c71237ee656b7028ab20f5921 package
  • LicenseRef-Notices-d1907587c823539bed1361211 package
1 more license expressions
  • LicenseRef-Notices-f5760bfd887ffc76b3654f6a1 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 →

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

Evidence