← Browse the extensions catalog

pg-ivm

Source README ↗

Overview

pg_ivm is an open-source extension that provides Incremental View Maintenance (IVM) for PostgreSQL, allowing materialized views to be updated incrementally when base tables change.

Package details

Extension version
1.17
Image built
Publisher
cloudnative-pg
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_ivm;
SQL version
1.17

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_ivm'

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-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 'main'

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 ↗

Maintained10

Determines if the project is "actively maintained".

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

Check details ↗

Token-PermissionsUnknown

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

Reasoning: No tokens 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-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 20 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: 0 out of 17 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 ↗

Contributors3

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

Reasoning: project has 1 contributing companies or organizations -- score normalized to 3

  • Info: found contributions from: sraoss

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

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

Check details ↗

Extension recipe
PostgreSQL

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

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

Unavailable

Overview

pg_ivm is an open-source extension that provides Incremental View Maintenance (IVM) for PostgreSQL, allowing materialized views to be updated incrementally when base tables change.

Package details

Extension version
1.17
Image built
Publisher
cloudnative-pg
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_ivm;
SQL version
1.17

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_ivm'

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-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 'main'

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 ↗

Maintained10

Determines if the project is "actively maintained".

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

Check details ↗

Token-PermissionsUnknown

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

Reasoning: No tokens 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-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 20 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: 0 out of 17 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 ↗

Contributors3

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

Reasoning: project has 1 contributing companies or organizations -- score normalized to 3

  • Info: found contributions from: sraoss

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

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

Check details ↗

Extension recipe
PostgreSQL

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

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

Unavailable

Overview

pg_ivm is an open-source extension that provides Incremental View Maintenance (IVM) for PostgreSQL, allowing materialized views to be updated incrementally when base tables change.

Package details

Extension version
1.17
Image built
Publisher
cloudnative-pg
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_ivm;
SQL version
1.17

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_ivm'

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-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 'main'

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 ↗

Maintained10

Determines if the project is "actively maintained".

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

Check details ↗

Token-PermissionsUnknown

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

Reasoning: No tokens 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-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 20 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: 0 out of 17 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 ↗

Contributors3

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

Reasoning: project has 1 contributing companies or organizations -- score normalized to 3

  • Info: found contributions from: sraoss

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

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

Check details ↗

Extension recipe
PostgreSQL

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

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

Unavailable

Overview

pg_ivm is an open-source extension that provides Incremental View Maintenance (IVM) for PostgreSQL, allowing materialized views to be updated incrementally when base tables change.

Package details

Extension version
1.17
Image built
Publisher
cloudnative-pg
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_ivm;
SQL version
1.17

PostgreSQL parameters

ParameterValue
shared_preload_libraries'pg_ivm'

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-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 'main'

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 ↗

Maintained10

Determines if the project is "actively maintained".

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

Check details ↗

Token-PermissionsUnknown

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

Reasoning: No tokens 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-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 20 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: 0 out of 17 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 ↗

Contributors3

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

Reasoning: project has 1 contributing companies or organizations -- score normalized to 3

  • Info: found contributions from: sraoss

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

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

Check details ↗

Extension recipe
PostgreSQL

This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.

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

Unavailable