← Browse the extensions catalog

roaringbitmap

Source README ↗

Overview

Provides compressed Roaring bitmap data structures and set operations for PostgreSQL. See the upstream project for its API and release history.

Package details

Extension version
1.2.0
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 roaringbitmap;
SQL version
1.2 — differs from extension version 1.2.0

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

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

Reasoning: branch protection is not maximal on development and all release branches

  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Warn: could not determine whether codeowners review is allowed
  • Warn: no status checks found to merge onto branch 'master'
  • Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings

Check details ↗

Code-Review2

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

Reasoning: Found 2/8 approved changesets -- score normalized to 2

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: 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10

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-test.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/build-test.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-test.yml:47: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-test.yml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: containerImage not pinned by hash: docker-example/Dockerfile:1: pin your Docker image by updating postgres:16.0-bookworm to postgres:16.0-bookworm@sha256:a80d0c1b119cf3d6bab27f72782f16e47ab8534ced937fa813ec2ab26e1fd81e
  • Warn: containerImage not pinned by hash: docker-example/Dockerfile:11: pin your Docker image by updating postgres:16.0-bookworm to postgres:16.0-bookworm@sha256:a80d0c1b119cf3d6bab27f72782f16e47ab8534ced937fa813ec2ab26e1fd81e
  • Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 1 third-party GitHubAction dependencies pinned
  • Info: 0 out of 2 containerImage 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-Tests8

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

Reasoning: 7 out of 8 merged PRs checked by a CI test -- score normalized to 8

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 ↗

Contributors6

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

Reasoning: project has 2 contributing companies or organizations -- score normalized to 6

  • Info: found contributions from: peakon, talkingdata

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

  • 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 →

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

Evidence

Overview

Provides compressed Roaring bitmap data structures and set operations for PostgreSQL. See the upstream project for its API and release history.

Package details

Extension version
1.2.0
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 roaringbitmap;
SQL version
1.2 — differs from extension version 1.2.0

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

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

Reasoning: branch protection is not maximal on development and all release branches

  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Warn: could not determine whether codeowners review is allowed
  • Warn: no status checks found to merge onto branch 'master'
  • Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings

Check details ↗

Code-Review2

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

Reasoning: Found 2/8 approved changesets -- score normalized to 2

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: 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10

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-test.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/build-test.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-test.yml:47: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-test.yml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: containerImage not pinned by hash: docker-example/Dockerfile:1: pin your Docker image by updating postgres:16.0-bookworm to postgres:16.0-bookworm@sha256:a80d0c1b119cf3d6bab27f72782f16e47ab8534ced937fa813ec2ab26e1fd81e
  • Warn: containerImage not pinned by hash: docker-example/Dockerfile:11: pin your Docker image by updating postgres:16.0-bookworm to postgres:16.0-bookworm@sha256:a80d0c1b119cf3d6bab27f72782f16e47ab8534ced937fa813ec2ab26e1fd81e
  • Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 1 third-party GitHubAction dependencies pinned
  • Info: 0 out of 2 containerImage 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-Tests8

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

Reasoning: 7 out of 8 merged PRs checked by a CI test -- score normalized to 8

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 ↗

Contributors6

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

Reasoning: project has 2 contributing companies or organizations -- score normalized to 6

  • Info: found contributions from: peakon, talkingdata

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

  • 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 →

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

Evidence

Overview

Provides compressed Roaring bitmap data structures and set operations for PostgreSQL. See the upstream project for its API and release history.

Package details

Extension version
1.2.0
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 roaringbitmap;
SQL version
1.2 — differs from extension version 1.2.0

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

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

Reasoning: branch protection is not maximal on development and all release branches

  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Warn: could not determine whether codeowners review is allowed
  • Warn: no status checks found to merge onto branch 'master'
  • Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings

Check details ↗

Code-Review2

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

Reasoning: Found 2/8 approved changesets -- score normalized to 2

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: 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10

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-test.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/build-test.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-test.yml:47: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-test.yml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: containerImage not pinned by hash: docker-example/Dockerfile:1: pin your Docker image by updating postgres:16.0-bookworm to postgres:16.0-bookworm@sha256:a80d0c1b119cf3d6bab27f72782f16e47ab8534ced937fa813ec2ab26e1fd81e
  • Warn: containerImage not pinned by hash: docker-example/Dockerfile:11: pin your Docker image by updating postgres:16.0-bookworm to postgres:16.0-bookworm@sha256:a80d0c1b119cf3d6bab27f72782f16e47ab8534ced937fa813ec2ab26e1fd81e
  • Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 1 third-party GitHubAction dependencies pinned
  • Info: 0 out of 2 containerImage 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-Tests8

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

Reasoning: 7 out of 8 merged PRs checked by a CI test -- score normalized to 8

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 ↗

Contributors6

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

Reasoning: project has 2 contributing companies or organizations -- score normalized to 6

  • Info: found contributions from: peakon, talkingdata

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

  • 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 →

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

Evidence

Overview

Provides compressed Roaring bitmap data structures and set operations for PostgreSQL. See the upstream project for its API and release history.

Package details

Extension version
1.2.0
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 roaringbitmap;
SQL version
1.2 — differs from extension version 1.2.0

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

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

Reasoning: branch protection is not maximal on development and all release branches

  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
  • Warn: could not determine whether codeowners review is allowed
  • Warn: no status checks found to merge onto branch 'master'
  • Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings

Check details ↗

Code-Review2

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

Reasoning: Found 2/8 approved changesets -- score normalized to 2

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: 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10

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-test.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/build-test.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-test.yml:47: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-test.yml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/ChenHuajun/pg_roaringbitmap/build-test.yml/master?enable=pin
  • Warn: containerImage not pinned by hash: docker-example/Dockerfile:1: pin your Docker image by updating postgres:16.0-bookworm to postgres:16.0-bookworm@sha256:a80d0c1b119cf3d6bab27f72782f16e47ab8534ced937fa813ec2ab26e1fd81e
  • Warn: containerImage not pinned by hash: docker-example/Dockerfile:11: pin your Docker image by updating postgres:16.0-bookworm to postgres:16.0-bookworm@sha256:a80d0c1b119cf3d6bab27f72782f16e47ab8534ced937fa813ec2ab26e1fd81e
  • Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
  • Info: 0 out of 1 third-party GitHubAction dependencies pinned
  • Info: 0 out of 2 containerImage 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-Tests8

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

Reasoning: 7 out of 8 merged PRs checked by a CI test -- score normalized to 8

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 ↗

Contributors6

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

Reasoning: project has 2 contributing companies or organizations -- score normalized to 6

  • Info: found contributions from: peakon, talkingdata

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

  • 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 →

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

Evidence