← Browse the extensions catalog

http

Source README ↗

Overview

http adds HTTP client functions to PostgreSQL so SQL can call HTTP services through libcurl. See the upstream project for the extension documentation.

Package details

Extension version
1.7.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 http;
SQL version
1.7 — differs from extension version 1.7.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-Protection0

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

Reasoning: branch protection not enabled on development/release branches

  • Warn: branch protection not enabled for branch 'master'

Check details ↗

Code-Review1

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

Reasoning: Found 3/27 approved changesets -- score normalized to 1

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

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/ci.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/ci.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/pramsey/pgsql-http/ci.yml/master?enable=pin
  • Info: 0 out of 1 GitHub-owned 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 7 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

Check details ↗

CI-Tests5

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

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

Check details ↗

CII-Best-Practices0

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

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

Check details ↗

Contributors10

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

Reasoning: project has 7 contributing companies or organizations

  • Info: found contributions from: PostgresApp, capacities, libgeos, pgRouting, pgedc, postgis, snowflakedb

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.md:0
  • Info: FSF or OSI recognized license: MIT License: LICENSE.md:0

Check details ↗

Extension recipe
MIT

License expressions in the shipped package inventory

  • MIT2 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
  • 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 MIT1 package
  • LicenseRef-4302abcc1ea1b6cbe8d19c79b892acf78878030220210707c19006828866207c1 package
  • LicenseRef-BSD3 AND ISC1 package
  • LicenseRef-Chromium AND MIT AND LicenseRef-gnulib1 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 →

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

Evidence

Overview

http adds HTTP client functions to PostgreSQL so SQL can call HTTP services through libcurl. See the upstream project for the extension documentation.

Package details

Extension version
1.7.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 http;
SQL version
1.7 — differs from extension version 1.7.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-Protection0

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

Reasoning: branch protection not enabled on development/release branches

  • Warn: branch protection not enabled for branch 'master'

Check details ↗

Code-Review1

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

Reasoning: Found 3/27 approved changesets -- score normalized to 1

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

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/ci.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/ci.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/pramsey/pgsql-http/ci.yml/master?enable=pin
  • Info: 0 out of 1 GitHub-owned 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 7 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

Check details ↗

CI-Tests5

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

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

Check details ↗

CII-Best-Practices0

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

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

Check details ↗

Contributors10

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

Reasoning: project has 7 contributing companies or organizations

  • Info: found contributions from: PostgresApp, capacities, libgeos, pgRouting, pgedc, postgis, snowflakedb

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.md:0
  • Info: FSF or OSI recognized license: MIT License: LICENSE.md:0

Check details ↗

Extension recipe
MIT

License expressions in the shipped package inventory

  • MIT2 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
  • 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 MIT1 package
  • LicenseRef-4302abcc1ea1b6cbe8d19c79b892acf78878030220210707c19006828866207c1 package
  • LicenseRef-BSD3 AND ISC1 package
  • LicenseRef-Chromium AND MIT AND LicenseRef-gnulib1 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 →

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

Evidence

Overview

http adds HTTP client functions to PostgreSQL so SQL can call HTTP services through libcurl. See the upstream project for the extension documentation.

Package details

Extension version
1.7.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 http;
SQL version
1.7 — differs from extension version 1.7.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-Protection0

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

Reasoning: branch protection not enabled on development/release branches

  • Warn: branch protection not enabled for branch 'master'

Check details ↗

Code-Review1

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

Reasoning: Found 3/27 approved changesets -- score normalized to 1

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

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/ci.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/ci.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/pramsey/pgsql-http/ci.yml/master?enable=pin
  • Info: 0 out of 1 GitHub-owned 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 7 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

Check details ↗

CI-Tests5

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

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

Check details ↗

CII-Best-Practices0

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

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

Check details ↗

Contributors10

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

Reasoning: project has 7 contributing companies or organizations

  • Info: found contributions from: PostgresApp, capacities, libgeos, pgRouting, pgedc, postgis, snowflakedb

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.md:0
  • Info: FSF or OSI recognized license: MIT License: LICENSE.md:0

Check details ↗

Extension recipe
MIT

License expressions in the shipped package inventory

  • MIT2 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
  • LicenseRef-4302abcc1ea1b6cbe8d19c79b892acf78878030220210707c19006828866207c1 package
  • LicenseRef-BSD31 package
  • LicenseRef-Chromium AND MIT AND LicenseRef-gnulib1 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 →

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

Evidence

Overview

http adds HTTP client functions to PostgreSQL so SQL can call HTTP services through libcurl. See the upstream project for the extension documentation.

Package details

Extension version
1.7.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 http;
SQL version
1.7 — differs from extension version 1.7.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-Protection0

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

Reasoning: branch protection not enabled on development/release branches

  • Warn: branch protection not enabled for branch 'master'

Check details ↗

Code-Review1

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

Reasoning: Found 3/27 approved changesets -- score normalized to 1

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

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/ci.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/ci.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/pramsey/pgsql-http/ci.yml/master?enable=pin
  • Info: 0 out of 1 GitHub-owned 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 7 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

Check details ↗

CI-Tests5

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

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

Check details ↗

CII-Best-Practices0

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

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

Check details ↗

Contributors10

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

Reasoning: project has 7 contributing companies or organizations

  • Info: found contributions from: PostgresApp, capacities, libgeos, pgRouting, pgedc, postgis, snowflakedb

Check details ↗

License10

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE.md:0
  • Info: FSF or OSI recognized license: MIT License: LICENSE.md:0

Check details ↗

Extension recipe
MIT

License expressions in the shipped package inventory

  • MIT2 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
  • LicenseRef-4302abcc1ea1b6cbe8d19c79b892acf78878030220210707c19006828866207c1 package
  • LicenseRef-BSD31 package
  • LicenseRef-Chromium AND MIT AND LicenseRef-gnulib1 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 →

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

Evidence