← Browse the extensions catalog

pg-hint-plan

Source README ↗

Overview

pg_hint_plan adds optimizer hints to PostgreSQL. Hints are written in SQL comments and can choose scan methods, join methods, and other planner behavior for individual queries.

Package details

Extension version
1.8.1
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_hint_plan;
SQL version
1.8.1

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_hint_plan'

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 · View OpenSSF report ↗

Dangerous-WorkflowUnknown

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

Reasoning: no workflows found

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

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

Reasoning: Found 0/30 approved changesets -- score normalized to 0

Check details ↗

Maintained5

Determines if the project is "actively maintained".

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

Check details ↗

Token-PermissionsUnknown

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

Reasoning: No tokens found

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-DependenciesUnknown

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

Reasoning: no dependencies found

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 2 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 ↗

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 ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: COPYRIGHT:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
NTT

License expressions in the shipped package inventory

  • LicenseRef-NTT AND PostgreSQL1 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 →

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

Evidence

Overview

pg_hint_plan adds optimizer hints to PostgreSQL. Hints are written in SQL comments and can choose scan methods, join methods, and other planner behavior for individual queries.

Package details

Extension version
1.8.1
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_hint_plan;
SQL version
1.8.1

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_hint_plan'

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 · View OpenSSF report ↗

Dangerous-WorkflowUnknown

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

Reasoning: no workflows found

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

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

Reasoning: Found 0/30 approved changesets -- score normalized to 0

Check details ↗

Maintained5

Determines if the project is "actively maintained".

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

Check details ↗

Token-PermissionsUnknown

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

Reasoning: No tokens found

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-DependenciesUnknown

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

Reasoning: no dependencies found

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 2 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 ↗

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 ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: COPYRIGHT:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
NTT

License expressions in the shipped package inventory

  • LicenseRef-NTT AND PostgreSQL1 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 →

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

Evidence

Overview

pg_hint_plan adds optimizer hints to PostgreSQL. Hints are written in SQL comments and can choose scan methods, join methods, and other planner behavior for individual queries.

Package details

Extension version
1.8.1
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_hint_plan;
SQL version
1.8.1

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_hint_plan'

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 · View OpenSSF report ↗

Dangerous-WorkflowUnknown

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

Reasoning: no workflows found

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

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

Reasoning: Found 0/30 approved changesets -- score normalized to 0

Check details ↗

Maintained5

Determines if the project is "actively maintained".

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

Check details ↗

Token-PermissionsUnknown

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

Reasoning: No tokens found

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-DependenciesUnknown

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

Reasoning: no dependencies found

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 2 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 ↗

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 ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: COPYRIGHT:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
NTT

License expressions in the shipped package inventory

  • LicenseRef-NTT AND PostgreSQL1 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 →

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

Evidence

Overview

pg_hint_plan adds optimizer hints to PostgreSQL. Hints are written in SQL comments and can choose scan methods, join methods, and other planner behavior for individual queries.

Package details

Extension version
1.8.1
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_hint_plan;
SQL version
1.8.1

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_hint_plan'

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 · View OpenSSF report ↗

Dangerous-WorkflowUnknown

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

Reasoning: no workflows found

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

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

Reasoning: Found 0/30 approved changesets -- score normalized to 0

Check details ↗

Maintained5

Determines if the project is "actively maintained".

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

Check details ↗

Token-PermissionsUnknown

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

Reasoning: No tokens found

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-DependenciesUnknown

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

Reasoning: no dependencies found

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 2 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 ↗

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 ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: COPYRIGHT:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
NTT

License expressions in the shipped package inventory

  • LicenseRef-NTT AND PostgreSQL1 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 →

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

Evidence