← Browse the extensions catalog

pg-jsonschema

Source README ↗

Overview

pg_jsonschema is a PostgreSQL extension that adds support for JSON Schema validation on the json and jsonb data types. JSON Schema describes the expected structure and constraints of JSON documents, allowing the extension to validate values, check schemas, and report validation errors directly in SQL.

Package details

Extension version
0.3.4
Image built
Publisher
cnpg-extensions
Build
PGRX
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_jsonschema;
SQL version
0.3.4

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

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Warn: codeowners review is required - but no codeowners file found in repo
  • Warn: 'last push approval' is disabled on branch 'master'
  • Warn: no status checks found to merge onto branch 'master'
  • Info: PRs are required in order to make changes on branch 'master'

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: :0

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 12 commit(s) and 0 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 ↗

Vulnerabilities3

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 7 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0190
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0385
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0253
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0441
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0386

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: containerImage not pinned by hash: dockerfiles/db/Dockerfile:1: pin your Docker image by updating postgres:16 to postgres:16@sha256:dd2bf3ce2dc83a81674cf7f217fcfd8a5009a4b325dda5b843bfee82a06cff6f
  • Warn: downloadThenRun not pinned by hash: dockerfiles/db/Dockerfile:23-27
  • Info: 0 out of 1 containerImage dependencies pinned
  • Info: 0 out of 1 downloadThenRun dependencies pinned

Check details ↗

SAST3

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 3

  • Warn: 10 commits out of 30 are checked with a SAST tool

Check details ↗

Security-Policy10

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Info: Found linked content: SECURITY.md:1
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

CI-Tests10

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

Reasoning: 12 out of 12 merged PRs checked by a CI test -- score normalized to 10

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 5 contributing companies or organizations

  • Info: found contributions from: Workato-All, anysphere, schemathesis, supabase, workato

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

  • MIT OR Apache-2.048 packages
  • MIT20 packages
  • Unicode-3.015 packages
  • Apache-2.0 OR MIT8 packages
  • Apache-2.02 packages
  • Unlicense OR MIT2 packages
  • Zlib2 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
4 more license expressions
  • Apache-2.0 OR BSL-1.01 package
  • BSD-2-Clause OR Apache-2.0 OR MIT1 package
  • GPL-2.0-only AND GPL-2.0-or-later AND LicenseRef-verbatim1 package
  • MIT-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 →

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

Evidence

Overview

pg_jsonschema is a PostgreSQL extension that adds support for JSON Schema validation on the json and jsonb data types. JSON Schema describes the expected structure and constraints of JSON documents, allowing the extension to validate values, check schemas, and report validation errors directly in SQL.

Package details

Extension version
0.3.4
Image built
Publisher
cnpg-extensions
Build
PGRX
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_jsonschema;
SQL version
0.3.4

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

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Warn: codeowners review is required - but no codeowners file found in repo
  • Warn: 'last push approval' is disabled on branch 'master'
  • Warn: no status checks found to merge onto branch 'master'
  • Info: PRs are required in order to make changes on branch 'master'

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: :0

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 12 commit(s) and 0 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 ↗

Vulnerabilities3

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 7 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0190
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0385
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0253
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0441
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0386

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: containerImage not pinned by hash: dockerfiles/db/Dockerfile:1: pin your Docker image by updating postgres:16 to postgres:16@sha256:dd2bf3ce2dc83a81674cf7f217fcfd8a5009a4b325dda5b843bfee82a06cff6f
  • Warn: downloadThenRun not pinned by hash: dockerfiles/db/Dockerfile:23-27
  • Info: 0 out of 1 containerImage dependencies pinned
  • Info: 0 out of 1 downloadThenRun dependencies pinned

Check details ↗

SAST3

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 3

  • Warn: 10 commits out of 30 are checked with a SAST tool

Check details ↗

Security-Policy10

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Info: Found linked content: SECURITY.md:1
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

CI-Tests10

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

Reasoning: 12 out of 12 merged PRs checked by a CI test -- score normalized to 10

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 5 contributing companies or organizations

  • Info: found contributions from: Workato-All, anysphere, schemathesis, supabase, workato

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

  • MIT OR Apache-2.048 packages
  • MIT20 packages
  • Unicode-3.015 packages
  • Apache-2.0 OR MIT8 packages
  • Apache-2.02 packages
  • Unlicense OR MIT2 packages
  • Zlib2 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
4 more license expressions
  • Apache-2.0 OR BSL-1.01 package
  • BSD-2-Clause OR Apache-2.0 OR MIT1 package
  • GPL-2.0-only AND GPL-2.0-or-later AND LicenseRef-verbatim1 package
  • MIT-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 →

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

Evidence

Overview

pg_jsonschema is a PostgreSQL extension that adds support for JSON Schema validation on the json and jsonb data types. JSON Schema describes the expected structure and constraints of JSON documents, allowing the extension to validate values, check schemas, and report validation errors directly in SQL.

Package details

Extension version
0.3.4
Image built
Publisher
cnpg-extensions
Build
PGRX
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_jsonschema;
SQL version
0.3.4

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

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Warn: codeowners review is required - but no codeowners file found in repo
  • Warn: 'last push approval' is disabled on branch 'master'
  • Warn: no status checks found to merge onto branch 'master'
  • Info: PRs are required in order to make changes on branch 'master'

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: :0

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 12 commit(s) and 0 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 ↗

Vulnerabilities3

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 7 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0190
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0385
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0253
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0441
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0386

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: containerImage not pinned by hash: dockerfiles/db/Dockerfile:1: pin your Docker image by updating postgres:16 to postgres:16@sha256:dd2bf3ce2dc83a81674cf7f217fcfd8a5009a4b325dda5b843bfee82a06cff6f
  • Warn: downloadThenRun not pinned by hash: dockerfiles/db/Dockerfile:23-27
  • Info: 0 out of 1 containerImage dependencies pinned
  • Info: 0 out of 1 downloadThenRun dependencies pinned

Check details ↗

SAST3

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 3

  • Warn: 10 commits out of 30 are checked with a SAST tool

Check details ↗

Security-Policy10

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Info: Found linked content: SECURITY.md:1
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

CI-Tests10

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

Reasoning: 12 out of 12 merged PRs checked by a CI test -- score normalized to 10

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 5 contributing companies or organizations

  • Info: found contributions from: Workato-All, anysphere, schemathesis, supabase, workato

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

  • MIT OR Apache-2.048 packages
  • MIT20 packages
  • Unicode-3.015 packages
  • Apache-2.0 OR MIT8 packages
  • Apache-2.02 packages
  • Unlicense OR MIT2 packages
  • Zlib2 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
4 more license expressions
  • Apache-2.0 OR BSL-1.01 package
  • BSD-2-Clause OR Apache-2.0 OR MIT1 package
  • LicenseRef-fd7e4aae7e7b05f217bcf2d02322825c360e66c52c4c2f1b28d784d6297a1c231 package
  • MIT-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 →

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

Evidence

Overview

pg_jsonschema is a PostgreSQL extension that adds support for JSON Schema validation on the json and jsonb data types. JSON Schema describes the expected structure and constraints of JSON documents, allowing the extension to validate values, check schemas, and report validation errors directly in SQL.

Package details

Extension version
0.3.4
Image built
Publisher
cnpg-extensions
Build
PGRX
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_jsonschema;
SQL version
0.3.4

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

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'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: required approving review count is 1 on branch 'master'
  • Warn: codeowners review is required - but no codeowners file found in repo
  • Warn: 'last push approval' is disabled on branch 'master'
  • Warn: no status checks found to merge onto branch 'master'
  • Info: PRs are required in order to make changes on branch 'master'

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: :0

Check details ↗

Maintained10

Determines if the project is "actively maintained".

Reasoning: 12 commit(s) and 0 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 ↗

Vulnerabilities3

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 7 existing vulnerabilities detected

  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0190
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0385
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0253
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0441
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0486
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2021-0127
  • Warn: Project is vulnerable to: https://osv.dev/RUSTSEC-2026-0386

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: containerImage not pinned by hash: dockerfiles/db/Dockerfile:1: pin your Docker image by updating postgres:16 to postgres:16@sha256:dd2bf3ce2dc83a81674cf7f217fcfd8a5009a4b325dda5b843bfee82a06cff6f
  • Warn: downloadThenRun not pinned by hash: dockerfiles/db/Dockerfile:23-27
  • Info: 0 out of 1 containerImage dependencies pinned
  • Info: 0 out of 1 downloadThenRun dependencies pinned

Check details ↗

SAST3

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 3

  • Warn: 10 commits out of 30 are checked with a SAST tool

Check details ↗

Security-Policy10

Determines if the project has published a security policy.

Reasoning: security policy file detected

  • Info: security policy file detected: SECURITY.md:1
  • Info: Found linked content: SECURITY.md:1
  • Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
  • Info: Found text in security policy: SECURITY.md:1

Check details ↗

CI-Tests10

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

Reasoning: 12 out of 12 merged PRs checked by a CI test -- score normalized to 10

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 5 contributing companies or organizations

  • Info: found contributions from: Workato-All, anysphere, schemathesis, supabase, workato

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

  • MIT OR Apache-2.048 packages
  • MIT20 packages
  • Unicode-3.015 packages
  • Apache-2.0 OR MIT8 packages
  • Apache-2.02 packages
  • Unlicense OR MIT2 packages
  • Zlib2 packages
  • (MIT OR Apache-2.0) AND Unicode-3.01 package
4 more license expressions
  • Apache-2.0 OR BSL-1.01 package
  • BSD-2-Clause OR Apache-2.0 OR MIT1 package
  • LicenseRef-fd7e4aae7e7b05f217bcf2d02322825c360e66c52c4c2f1b28d784d6297a1c231 package
  • MIT-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 →

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

Evidence