← Browse the extensions catalog

pgsphere

Source README ↗

Overview

pgSphere is a PostgreSQL extension that provides spherical geometry data types and operators for astronomical and geographical data. It supports types such as spherical points, circles, ellipses, lines, polygons, and boxes, along with indexing via GiST.

Package details

Extension version
1.5.2
Image built
Publisher
cnpg-extensions
Build
Debian
Platform
PG 18 · Trixie · amd64

Project links

Links from package metadata, recipe update rules, or reviewed upstream mappings.

Database setup

Required extensions
None specified
SQL installation
CREATE EXTENSION pg_sphere;
SQL version
1.5.2

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

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

Reasoning: all changesets reviewed

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: .github/dependabot.yml:1

Check details ↗

Maintained7

Determines if the project is "actively maintained".

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

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/build-and-check-windows-latest.yml:1
  • Warn: no topLevel permission defined: .github/workflows/build-and-check.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: third-party GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:57: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:88: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:75: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:78: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:45: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:51: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Info: 0 out of 8 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 2 third-party GitHubAction 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-Tests0

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

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

Check details ↗

CII-Best-Practices0

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

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

Reasoning: project has 8 contributing companies or organizations

  • Info: found contributions from: Debian, cybertec-postgresql, debian, gearman, nasa/goddard space flight center, oftc, powa-team, supabase

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: COPYRIGHT.pg_sphere:0
  • Info: FSF or OSI recognized license: BSD 3-Clause "New" or "Revised" License: COPYRIGHT.pg_sphere:0

Check details ↗

Extension recipe
GPL-3+

License expressions in the shipped package inventory

  • FSFAP AND FSFUL AND FSFULLR AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later AND MIT3 packages
  • LicenseRef-20390f8a6f3b1e4d7cb45dd8652dabb259bbef688cbad839bcdb0b9ba7252f792 packages
  • BSD-2-Clause AND LicenseRef-Expat AND GPL-3.0-only AND GPL-3.0-or-later AND MIT AND LicenseRef-all-permissive1 package
  • BSD-3-Clause AND BSD-3-Clause AND BSD-4-Clause-UC AND FSFULLR AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND ISC AND OLDAP-2.8 AND X11 AND curl1 package
  • BSD-3-Clause AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later1 package
  • BSD-3-Clause AND GPL-3.0-only AND GPL-3.0-or-later1 package
  • FSFAP AND FSFUL AND FSFULLR AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later AND LGPL-2.0-only AND LGPL-2.0-or-later AND LicenseRef-NOSA AND LicenseRef-SAO AND X11 AND LicenseRef-cfortran1 package
  • GPL-2.0-only AND GPL-2.0-or-later1 package
4 more license expressions
  • LicenseRef-4302abcc1ea1b6cbe8d19c79b892acf78878030220210707c19006828866207c1 package
  • LicenseRef-BSD3 AND ISC1 package
  • LicenseRef-Chromium AND MIT AND LicenseRef-gnulib1 package
  • MIT1 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 →

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

Evidence

Overview

pgSphere is a PostgreSQL extension that provides spherical geometry data types and operators for astronomical and geographical data. It supports types such as spherical points, circles, ellipses, lines, polygons, and boxes, along with indexing via GiST.

Package details

Extension version
1.5.2
Image built
Publisher
cnpg-extensions
Build
Debian
Platform
PG 18 · Trixie · arm64

Project links

Links from package metadata, recipe update rules, or reviewed upstream mappings.

Database setup

Required extensions
None specified
SQL installation
CREATE EXTENSION pg_sphere;
SQL version
1.5.2

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

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

Reasoning: all changesets reviewed

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: .github/dependabot.yml:1

Check details ↗

Maintained7

Determines if the project is "actively maintained".

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

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/build-and-check-windows-latest.yml:1
  • Warn: no topLevel permission defined: .github/workflows/build-and-check.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: third-party GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:57: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:88: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:75: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:78: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:45: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:51: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Info: 0 out of 8 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 2 third-party GitHubAction 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-Tests0

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

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

Check details ↗

CII-Best-Practices0

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

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

Reasoning: project has 8 contributing companies or organizations

  • Info: found contributions from: Debian, cybertec-postgresql, debian, gearman, nasa/goddard space flight center, oftc, powa-team, supabase

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: COPYRIGHT.pg_sphere:0
  • Info: FSF or OSI recognized license: BSD 3-Clause "New" or "Revised" License: COPYRIGHT.pg_sphere:0

Check details ↗

Extension recipe
GPL-3+

License expressions in the shipped package inventory

  • FSFAP AND FSFUL AND FSFULLR AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later AND MIT3 packages
  • LicenseRef-20390f8a6f3b1e4d7cb45dd8652dabb259bbef688cbad839bcdb0b9ba7252f792 packages
  • BSD-2-Clause AND LicenseRef-Expat AND GPL-3.0-only AND GPL-3.0-or-later AND MIT AND LicenseRef-all-permissive1 package
  • BSD-3-Clause AND BSD-3-Clause AND BSD-4-Clause-UC AND FSFULLR AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND ISC AND OLDAP-2.8 AND X11 AND curl1 package
  • BSD-3-Clause AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later1 package
  • BSD-3-Clause AND GPL-3.0-only AND GPL-3.0-or-later1 package
  • FSFAP AND FSFUL AND FSFULLR AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later AND LGPL-2.0-only AND LGPL-2.0-or-later AND LicenseRef-NOSA AND LicenseRef-SAO AND X11 AND LicenseRef-cfortran1 package
  • GPL-2.0-only AND GPL-2.0-or-later1 package
4 more license expressions
  • LicenseRef-4302abcc1ea1b6cbe8d19c79b892acf78878030220210707c19006828866207c1 package
  • LicenseRef-BSD3 AND ISC1 package
  • LicenseRef-Chromium AND MIT AND LicenseRef-gnulib1 package
  • MIT1 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 →

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

Evidence

Overview

pgSphere is a PostgreSQL extension that provides spherical geometry data types and operators for astronomical and geographical data. It supports types such as spherical points, circles, ellipses, lines, polygons, and boxes, along with indexing via GiST.

Package details

Extension version
1.5.2
Image built
Publisher
cnpg-extensions
Build
Debian
Platform
PG 18 · Bookworm · amd64

Project links

Links from package metadata, recipe update rules, or reviewed upstream mappings.

Database setup

Required extensions
None specified
SQL installation
CREATE EXTENSION pg_sphere;
SQL version
1.5.2

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

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

Reasoning: all changesets reviewed

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: .github/dependabot.yml:1

Check details ↗

Maintained7

Determines if the project is "actively maintained".

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

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/build-and-check-windows-latest.yml:1
  • Warn: no topLevel permission defined: .github/workflows/build-and-check.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: third-party GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:57: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:88: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:75: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:78: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:45: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:51: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Info: 0 out of 8 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 2 third-party GitHubAction 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-Tests0

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

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

Check details ↗

CII-Best-Practices0

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

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

Reasoning: project has 8 contributing companies or organizations

  • Info: found contributions from: Debian, cybertec-postgresql, debian, gearman, nasa/goddard space flight center, oftc, powa-team, supabase

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: COPYRIGHT.pg_sphere:0
  • Info: FSF or OSI recognized license: BSD 3-Clause "New" or "Revised" License: COPYRIGHT.pg_sphere:0

Check details ↗

Extension recipe
GPL-3+

License expressions in the shipped package inventory

  • LicenseRef-da8191658b3452ce9caf31638ba61dab31a38c619fa39df119812e050f592fd32 packages
  • BSD-2-Clause AND LicenseRef-Expat AND GPL-3.0-only AND GPL-3.0-or-later AND MIT AND LicenseRef-all-permissive1 package
  • BSD-3-Clause AND BSD-3-Clause AND BSD-4-Clause-UC AND FSFULLR AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND ISC AND OLDAP-2.8 AND X11 AND curl1 package
  • BSD-3-Clause AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later1 package
  • BSD-3-Clause AND GPL-3.0-only AND GPL-3.0-or-later1 package
  • GPL-2.0-only AND GPL-2.0-or-later1 package
  • LicenseRef-4302abcc1ea1b6cbe8d19c79b892acf78878030220210707c19006828866207c1 package
  • LicenseRef-53f9aee79bcd00cf7517e13d0f5500cb49b8e593b8f6913a38460cd1e5dc1d6e1 package
3 more license expressions
  • LicenseRef-BSD31 package
  • LicenseRef-Chromium AND MIT AND LicenseRef-gnulib1 package
  • MIT1 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 →

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

Evidence

Overview

pgSphere is a PostgreSQL extension that provides spherical geometry data types and operators for astronomical and geographical data. It supports types such as spherical points, circles, ellipses, lines, polygons, and boxes, along with indexing via GiST.

Package details

Extension version
1.5.2
Image built
Publisher
cnpg-extensions
Build
Debian
Platform
PG 18 · Bookworm · arm64

Project links

Links from package metadata, recipe update rules, or reviewed upstream mappings.

Database setup

Required extensions
None specified
SQL installation
CREATE EXTENSION pg_sphere;
SQL version
1.5.2

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

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

Reasoning: all changesets reviewed

Check details ↗

Dependency-Update-Tool10

Determines if the project uses a dependency update tool.

Reasoning: update tool detected

  • Info: detected update tool: Dependabot: .github/dependabot.yml:1

Check details ↗

Maintained7

Determines if the project is "actively maintained".

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

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/build-and-check-windows-latest.yml:1
  • Warn: no topLevel permission defined: .github/workflows/build-and-check.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: third-party GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:57: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check-windows-latest.yml:88: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check-windows-latest.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:75: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-check.yml:78: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/build-and-check.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:45: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deploy-docs.yml:51: update your workflow using https://app.stepsecurity.io/secureworkflow/postgrespro/pgsphere/deploy-docs.yml/master?enable=pin
  • Info: 0 out of 8 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 2 third-party GitHubAction 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-Tests0

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

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

Check details ↗

CII-Best-Practices0

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

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

Reasoning: project has 8 contributing companies or organizations

  • Info: found contributions from: Debian, cybertec-postgresql, debian, gearman, nasa/goddard space flight center, oftc, powa-team, supabase

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: COPYRIGHT.pg_sphere:0
  • Info: FSF or OSI recognized license: BSD 3-Clause "New" or "Revised" License: COPYRIGHT.pg_sphere:0

Check details ↗

Extension recipe
GPL-3+

License expressions in the shipped package inventory

  • LicenseRef-da8191658b3452ce9caf31638ba61dab31a38c619fa39df119812e050f592fd32 packages
  • BSD-2-Clause AND LicenseRef-Expat AND GPL-3.0-only AND GPL-3.0-or-later AND MIT AND LicenseRef-all-permissive1 package
  • BSD-3-Clause AND BSD-3-Clause AND BSD-4-Clause-UC AND FSFULLR AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND ISC AND OLDAP-2.8 AND X11 AND curl1 package
  • BSD-3-Clause AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later1 package
  • BSD-3-Clause AND GPL-3.0-only AND GPL-3.0-or-later1 package
  • GPL-2.0-only AND GPL-2.0-or-later1 package
  • LicenseRef-4302abcc1ea1b6cbe8d19c79b892acf78878030220210707c19006828866207c1 package
  • LicenseRef-53f9aee79bcd00cf7517e13d0f5500cb49b8e593b8f6913a38460cd1e5dc1d6e1 package
3 more license expressions
  • LicenseRef-BSD31 package
  • LicenseRef-Chromium AND MIT AND LicenseRef-gnulib1 package
  • MIT1 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 →

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

Evidence