← Browse the extensions catalog

pg-graphql

Source README ↗

Overview

pg_graphql adds GraphQL support to PostgreSQL. It reflects the SQL schema and exposes it through the graphql.resolve(...) SQL function, so clients can query the database with GraphQL without a separate application server. This image supports PostgreSQL 18 on Debian bookworm and trixie.

Package details

Extension version
1.6.3
Image built
Publisher
cnpg-extensions
Build
PGRX
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_graphql;
SQL version
1.6.3

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Info: codeowner review is 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-Review7

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

Reasoning: Found 13/17 approved changesets -- score normalized to 7

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: :0

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 19 commit(s) and 0 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: topLevel 'contents' permission set to 'write': .github/workflows/coverage.yml:10
  • Info: found token with 'none' permissions: .github/workflows/docs.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pre-commit.yaml:7
  • Warn: topLevel 'contents' permission set to 'write': .github/workflows/release.yml:10
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/test.yml:7
  • Info: no jobLevel write permissions found

Check details ↗

Vulnerabilities3

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 7 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0190
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0385
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2024-0384
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0441
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0386

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-Dependencies4

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

Reasoning: dependency not pinned by hash detected -- score normalized to 4

  • Warn: containerImage not pinned by hash: dockerfiles/db/Dockerfile:2: pin your Docker image by updating postgres:18 to postgres:18@sha256:2ea8630df176ad090ec92136dee850397c5af8781e4bcf2e4162593691c61bbc
  • Warn: downloadThenRun not pinned by hash: dockerfiles/db/Dockerfile:24-28
  • Warn: pipCommand not pinned by hash: .github/workflows/pre-commit.yaml:24
  • Warn: pipCommand not pinned by hash: .github/workflows/pre-commit.yaml:25
  • Warn: downloadThenRun not pinned by hash: .github/workflows/release.yml:77
  • Info: 11 out of 11 GitHub-owned GitHubAction dependencies pinned
  • Info: 3 out of 3 third-party GitHubAction dependencies pinned
  • Info: 0 out of 1 containerImage dependencies pinned
  • Info: 0 out of 2 downloadThenRun dependencies pinned
  • Info: 0 out of 2 pipCommand dependencies pinned

Check details ↗

SAST6

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 6

  • Warn: 18 commits out of 26 are checked with a SAST tool

Check details ↗

Security-Policy10

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Info: Found linked content: SECURITY.md:1
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

CI-Tests10

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

Reasoning: 13 out of 13 merged PRs checked by a CI test -- score normalized to 10

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

  • Info: found contributions from: Spawnfest2012, TeamTechtris, abnormal ai, agner, beamjs, hanover park, implementable, inferaldata, oftn-oswg, postgres @ supabase, sit-fyi, starbucks | @themoralcodeorg, supabase, veridit, veridit as, zeromq

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: Apache License 2.0: LICENSE:0

Check details ↗

Extension recipe
Apache-2.0

License expressions in the shipped package inventory

  • MIT OR Apache-2.035 packages
  • MIT16 packages
  • Apache-2.0 OR MIT4 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
  • Apache-2.01 package
  • BSD-3-Clause1 package
  • Unlicense OR MIT1 package
  • Zlib1 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 →

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

Evidence

Overview

pg_graphql adds GraphQL support to PostgreSQL. It reflects the SQL schema and exposes it through the graphql.resolve(...) SQL function, so clients can query the database with GraphQL without a separate application server. This image supports PostgreSQL 18 on Debian bookworm and trixie.

Package details

Extension version
1.6.3
Image built
Publisher
cnpg-extensions
Build
PGRX
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_graphql;
SQL version
1.6.3

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Info: codeowner review is 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-Review7

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

Reasoning: Found 13/17 approved changesets -- score normalized to 7

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: :0

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 19 commit(s) and 0 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: topLevel 'contents' permission set to 'write': .github/workflows/coverage.yml:10
  • Info: found token with 'none' permissions: .github/workflows/docs.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pre-commit.yaml:7
  • Warn: topLevel 'contents' permission set to 'write': .github/workflows/release.yml:10
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/test.yml:7
  • Info: no jobLevel write permissions found

Check details ↗

Vulnerabilities3

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 7 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0190
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0385
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2024-0384
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0441
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0386

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-Dependencies4

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

Reasoning: dependency not pinned by hash detected -- score normalized to 4

  • Warn: containerImage not pinned by hash: dockerfiles/db/Dockerfile:2: pin your Docker image by updating postgres:18 to postgres:18@sha256:2ea8630df176ad090ec92136dee850397c5af8781e4bcf2e4162593691c61bbc
  • Warn: downloadThenRun not pinned by hash: dockerfiles/db/Dockerfile:24-28
  • Warn: pipCommand not pinned by hash: .github/workflows/pre-commit.yaml:24
  • Warn: pipCommand not pinned by hash: .github/workflows/pre-commit.yaml:25
  • Warn: downloadThenRun not pinned by hash: .github/workflows/release.yml:77
  • Info: 11 out of 11 GitHub-owned GitHubAction dependencies pinned
  • Info: 3 out of 3 third-party GitHubAction dependencies pinned
  • Info: 0 out of 1 containerImage dependencies pinned
  • Info: 0 out of 2 downloadThenRun dependencies pinned
  • Info: 0 out of 2 pipCommand dependencies pinned

Check details ↗

SAST6

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 6

  • Warn: 18 commits out of 26 are checked with a SAST tool

Check details ↗

Security-Policy10

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Info: Found linked content: SECURITY.md:1
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

CI-Tests10

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

Reasoning: 13 out of 13 merged PRs checked by a CI test -- score normalized to 10

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

  • Info: found contributions from: Spawnfest2012, TeamTechtris, abnormal ai, agner, beamjs, hanover park, implementable, inferaldata, oftn-oswg, postgres @ supabase, sit-fyi, starbucks | @themoralcodeorg, supabase, veridit, veridit as, zeromq

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: Apache License 2.0: LICENSE:0

Check details ↗

Extension recipe
Apache-2.0

License expressions in the shipped package inventory

  • MIT OR Apache-2.034 packages
  • MIT16 packages
  • Apache-2.0 OR MIT4 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
  • Apache-2.01 package
  • BSD-3-Clause1 package
  • Unlicense OR MIT1 package
  • Zlib1 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 →

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

Evidence

Overview

pg_graphql adds GraphQL support to PostgreSQL. It reflects the SQL schema and exposes it through the graphql.resolve(...) SQL function, so clients can query the database with GraphQL without a separate application server. This image supports PostgreSQL 18 on Debian bookworm and trixie.

Package details

Extension version
1.6.3
Image built
Publisher
cnpg-extensions
Build
PGRX
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_graphql;
SQL version
1.6.3

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Info: codeowner review is 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-Review7

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

Reasoning: Found 13/17 approved changesets -- score normalized to 7

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: :0

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 19 commit(s) and 0 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: topLevel 'contents' permission set to 'write': .github/workflows/coverage.yml:10
  • Info: found token with 'none' permissions: .github/workflows/docs.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pre-commit.yaml:7
  • Warn: topLevel 'contents' permission set to 'write': .github/workflows/release.yml:10
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/test.yml:7
  • Info: no jobLevel write permissions found

Check details ↗

Vulnerabilities3

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 7 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0190
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0385
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2024-0384
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0441
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0386

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-Dependencies4

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

Reasoning: dependency not pinned by hash detected -- score normalized to 4

  • Warn: containerImage not pinned by hash: dockerfiles/db/Dockerfile:2: pin your Docker image by updating postgres:18 to postgres:18@sha256:2ea8630df176ad090ec92136dee850397c5af8781e4bcf2e4162593691c61bbc
  • Warn: downloadThenRun not pinned by hash: dockerfiles/db/Dockerfile:24-28
  • Warn: pipCommand not pinned by hash: .github/workflows/pre-commit.yaml:24
  • Warn: pipCommand not pinned by hash: .github/workflows/pre-commit.yaml:25
  • Warn: downloadThenRun not pinned by hash: .github/workflows/release.yml:77
  • Info: 11 out of 11 GitHub-owned GitHubAction dependencies pinned
  • Info: 3 out of 3 third-party GitHubAction dependencies pinned
  • Info: 0 out of 1 containerImage dependencies pinned
  • Info: 0 out of 2 downloadThenRun dependencies pinned
  • Info: 0 out of 2 pipCommand dependencies pinned

Check details ↗

SAST6

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 6

  • Warn: 18 commits out of 26 are checked with a SAST tool

Check details ↗

Security-Policy10

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Info: Found linked content: SECURITY.md:1
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

CI-Tests10

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

Reasoning: 13 out of 13 merged PRs checked by a CI test -- score normalized to 10

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

  • Info: found contributions from: Spawnfest2012, TeamTechtris, abnormal ai, agner, beamjs, hanover park, implementable, inferaldata, oftn-oswg, postgres @ supabase, sit-fyi, starbucks | @themoralcodeorg, supabase, veridit, veridit as, zeromq

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: Apache License 2.0: LICENSE:0

Check details ↗

Extension recipe
Apache-2.0

License expressions in the shipped package inventory

  • MIT OR Apache-2.035 packages
  • MIT16 packages
  • Apache-2.0 OR MIT4 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
  • Apache-2.01 package
  • BSD-3-Clause1 package
  • Unlicense OR MIT1 package
  • Zlib1 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 →

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

Evidence

Overview

pg_graphql adds GraphQL support to PostgreSQL. It reflects the SQL schema and exposes it through the graphql.resolve(...) SQL function, so clients can query the database with GraphQL without a separate application server. This image supports PostgreSQL 18 on Debian bookworm and trixie.

Package details

Extension version
1.6.3
Image built
Publisher
cnpg-extensions
Build
PGRX
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_graphql;
SQL version
1.6.3

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Info: codeowner review is 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-Review7

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

Reasoning: Found 13/17 approved changesets -- score normalized to 7

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: :0

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 19 commit(s) and 0 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: topLevel 'contents' permission set to 'write': .github/workflows/coverage.yml:10
  • Info: found token with 'none' permissions: .github/workflows/docs.yml:1
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/pre-commit.yaml:7
  • Warn: topLevel 'contents' permission set to 'write': .github/workflows/release.yml:10
  • Info: topLevel 'contents' permission set to 'read': .github/workflows/test.yml:7
  • Info: no jobLevel write permissions found

Check details ↗

Vulnerabilities3

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 7 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0190
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0385
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2024-0384
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0441
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0386

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-Dependencies4

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

Reasoning: dependency not pinned by hash detected -- score normalized to 4

  • Warn: containerImage not pinned by hash: dockerfiles/db/Dockerfile:2: pin your Docker image by updating postgres:18 to postgres:18@sha256:2ea8630df176ad090ec92136dee850397c5af8781e4bcf2e4162593691c61bbc
  • Warn: downloadThenRun not pinned by hash: dockerfiles/db/Dockerfile:24-28
  • Warn: pipCommand not pinned by hash: .github/workflows/pre-commit.yaml:24
  • Warn: pipCommand not pinned by hash: .github/workflows/pre-commit.yaml:25
  • Warn: downloadThenRun not pinned by hash: .github/workflows/release.yml:77
  • Info: 11 out of 11 GitHub-owned GitHubAction dependencies pinned
  • Info: 3 out of 3 third-party GitHubAction dependencies pinned
  • Info: 0 out of 1 containerImage dependencies pinned
  • Info: 0 out of 2 downloadThenRun dependencies pinned
  • Info: 0 out of 2 pipCommand dependencies pinned

Check details ↗

SAST6

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 6

  • Warn: 18 commits out of 26 are checked with a SAST tool

Check details ↗

Security-Policy10

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Info: Found linked content: SECURITY.md:1
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

CI-Tests10

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

Reasoning: 13 out of 13 merged PRs checked by a CI test -- score normalized to 10

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

  • Info: found contributions from: Spawnfest2012, TeamTechtris, abnormal ai, agner, beamjs, hanover park, implementable, inferaldata, oftn-oswg, postgres @ supabase, sit-fyi, starbucks | @themoralcodeorg, supabase, veridit, veridit as, zeromq

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: Apache License 2.0: LICENSE:0

Check details ↗

Extension recipe
Apache-2.0

License expressions in the shipped package inventory

  • MIT OR Apache-2.034 packages
  • MIT16 packages
  • Apache-2.0 OR MIT4 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
  • Apache-2.01 package
  • BSD-3-Clause1 package
  • Unlicense OR MIT1 package
  • Zlib1 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 →

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

Evidence