← Browse the extensions catalog

h3

Source README ↗

Overview

h3-pg is a PostgreSQL extension that binds the Uber H3 hierarchical hexagonal geospatial indexing system to PostgreSQL. It enables efficient geospatial analysis using H3 cell indexes.

Package details

Extension version
4.2.3
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 h3;
SQL version
4.2.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-ProtectionUnknown

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md

Check details ↗

Code-Review2

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

Reasoning: Found 3/14 approved changesets -- score normalized to 2

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 ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-Permissions0

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

Reasoning: detected GitHub workflow tokens with excessive permissions

  • Warn: no topLevel permission defined: .github/workflows/documentation.yml:1
  • Warn: no topLevel permission defined: .github/workflows/pgxn.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-linux.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-macos.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-windows.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/documentation.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/documentation.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/documentation.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/documentation.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pgxn.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/pgxn.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-linux.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-linux.yml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/test-linux.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-linux.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-macos.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-macos.yml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/test-macos.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-macos.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-windows.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-windows.yml/main?enable=pin
  • Warn: pipCommand not pinned by hash: .github/workflows/pgxn.yml:18
  • Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 2 third-party GitHubAction dependencies pinned
  • Info: 0 out of 1 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 29 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-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 21 contributing companies or organizations

  • Info: found contributions from: CodeAndBeats, FACTORYX, basecamp, genomejs, gulp-community, gulpjs, hackphx-arduinowearables, konturio, kothic, libgeos, minsk-hackerspace, ndjson, osm-ru-board, parks-foundation, pgRouting, postgis, rayo, revisitors, shastajs, tilemill-project, wearefractal

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

  • AGPL-3.0-or-later AND Apache-2.0 AND LicenseRef-sqlite1 package
  • Apache-2.01 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

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

Evidence

Overview

h3-pg is a PostgreSQL extension that binds the Uber H3 hierarchical hexagonal geospatial indexing system to PostgreSQL. It enables efficient geospatial analysis using H3 cell indexes.

Package details

Extension version
4.2.3
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 h3;
SQL version
4.2.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-ProtectionUnknown

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md

Check details ↗

Code-Review2

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

Reasoning: Found 3/14 approved changesets -- score normalized to 2

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 ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-Permissions0

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

Reasoning: detected GitHub workflow tokens with excessive permissions

  • Warn: no topLevel permission defined: .github/workflows/documentation.yml:1
  • Warn: no topLevel permission defined: .github/workflows/pgxn.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-linux.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-macos.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-windows.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/documentation.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/documentation.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/documentation.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/documentation.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pgxn.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/pgxn.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-linux.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-linux.yml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/test-linux.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-linux.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-macos.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-macos.yml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/test-macos.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-macos.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-windows.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-windows.yml/main?enable=pin
  • Warn: pipCommand not pinned by hash: .github/workflows/pgxn.yml:18
  • Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 2 third-party GitHubAction dependencies pinned
  • Info: 0 out of 1 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 29 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-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 21 contributing companies or organizations

  • Info: found contributions from: CodeAndBeats, FACTORYX, basecamp, genomejs, gulp-community, gulpjs, hackphx-arduinowearables, konturio, kothic, libgeos, minsk-hackerspace, ndjson, osm-ru-board, parks-foundation, pgRouting, postgis, rayo, revisitors, shastajs, tilemill-project, wearefractal

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

  • AGPL-3.0-or-later AND Apache-2.0 AND LicenseRef-sqlite1 package
  • Apache-2.01 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

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

Evidence

Overview

h3-pg is a PostgreSQL extension that binds the Uber H3 hierarchical hexagonal geospatial indexing system to PostgreSQL. It enables efficient geospatial analysis using H3 cell indexes.

Package details

Extension version
4.2.3
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 h3;
SQL version
4.2.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-ProtectionUnknown

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md

Check details ↗

Code-Review2

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

Reasoning: Found 3/14 approved changesets -- score normalized to 2

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 ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-Permissions0

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

Reasoning: detected GitHub workflow tokens with excessive permissions

  • Warn: no topLevel permission defined: .github/workflows/documentation.yml:1
  • Warn: no topLevel permission defined: .github/workflows/pgxn.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-linux.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-macos.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-windows.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/documentation.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/documentation.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/documentation.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/documentation.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pgxn.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/pgxn.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-linux.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-linux.yml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/test-linux.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-linux.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-macos.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-macos.yml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/test-macos.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-macos.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-windows.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-windows.yml/main?enable=pin
  • Warn: pipCommand not pinned by hash: .github/workflows/pgxn.yml:18
  • Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 2 third-party GitHubAction dependencies pinned
  • Info: 0 out of 1 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 29 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-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 21 contributing companies or organizations

  • Info: found contributions from: CodeAndBeats, FACTORYX, basecamp, genomejs, gulp-community, gulpjs, hackphx-arduinowearables, konturio, kothic, libgeos, minsk-hackerspace, ndjson, osm-ru-board, parks-foundation, pgRouting, postgis, rayo, revisitors, shastajs, tilemill-project, wearefractal

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

  • AGPL-3.0-or-later AND Apache-2.0 AND LicenseRef-sqlite1 package
  • Apache-2.01 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

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

Evidence

Overview

h3-pg is a PostgreSQL extension that binds the Uber H3 hierarchical hexagonal geospatial indexing system to PostgreSQL. It enables efficient geospatial analysis using H3 cell indexes.

Package details

Extension version
4.2.3
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 h3;
SQL version
4.2.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-ProtectionUnknown

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md

Check details ↗

Code-Review2

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

Reasoning: Found 3/14 approved changesets -- score normalized to 2

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 ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-Permissions0

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

Reasoning: detected GitHub workflow tokens with excessive permissions

  • Warn: no topLevel permission defined: .github/workflows/documentation.yml:1
  • Warn: no topLevel permission defined: .github/workflows/pgxn.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-linux.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-macos.yml:1
  • Warn: no topLevel permission defined: .github/workflows/test-windows.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/documentation.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/documentation.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/documentation.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/documentation.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pgxn.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/pgxn.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-linux.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-linux.yml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/test-linux.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-linux.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-macos.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-macos.yml/main?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/test-macos.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-macos.yml/main?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-windows.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/postgis/h3-pg/test-windows.yml/main?enable=pin
  • Warn: pipCommand not pinned by hash: .github/workflows/pgxn.yml:18
  • Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 2 third-party GitHubAction dependencies pinned
  • Info: 0 out of 1 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 29 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-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 21 contributing companies or organizations

  • Info: found contributions from: CodeAndBeats, FACTORYX, basecamp, genomejs, gulp-community, gulpjs, hackphx-arduinowearables, konturio, kothic, libgeos, minsk-hackerspace, ndjson, osm-ru-board, parks-foundation, pgRouting, postgis, rayo, revisitors, shastajs, tilemill-project, wearefractal

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

  • AGPL-3.0-or-later AND Apache-2.0 AND LicenseRef-sqlite1 package
  • Apache-2.01 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

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

Evidence