schemastore.py
A collection of all JSON Schemas from the schemastore.org catalog, installable so they may be used without internet access.
Installation
Use your favorite package manager, e.g. via:
$ uv pip install schemastore
or
$ pip install schemastore
Usage
Schemas are made usable as a referencing.Registry.
It is available as:
import schemastore
registry = schemastore.registry()
and use any of the API from the aforementioned referencing package to make use of the schemas, such as:
print(registry.get_or_retrieve("https://json.schemastore.org/github-action.json").value)
though more typically you will use the registry alongside a JSON Schema validator such as those provided by the jsonschema library:
import jsonschema
import schemastore
# Validate whether the string "foo" is a valid GitHub actions workflow (it is not.)
jsonschema.validate(
'"foo"',
{"$ref": "https://json.schemastore.org/github-action.json"},
registry=schemastore.registry(),
)
2 maintainers
Metadata
2 maintainers
Release files for schemastore 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| schemastore-0.2.3.tar.gz | 6.1 MB | With provenance | Details for schemastore-0.2.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| schemastore-0.2.3-py3-none-any.whl | Python 3 | none | any | Details for schemastore-0.2.3-py3-none-any.whl |
Total release size: 8.8 MB
Release files / schemastore-0.2.3.tar.gz
| Download URL | schemastore-0.2.3.tar.gz |
|---|---|
| Size | 6.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
904c4e5df11968c5c3cf91d08a2b7f5f833a3f449fca80470c395154aea8a1d2
|
|
BLAKE2b-256 checksum How to use checksums |
dae1999c99abac1cefad1a92559c92fcab3ce17847a5b44f95737f3520d5d138
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 28, 2025.
Transparency logRelease files / schemastore-0.2.3-py3-none-any.whl
| Download URL | schemastore-0.2.3-py3-none-any.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
049b62589e7cc3a11fa5d1977cdbf0524cf1c905a81cd0f9d27075b7578cf2d3
|
|
BLAKE2b-256 checksum How to use checksums |
ce312d9c3ed7046c6869efb23a9d48e8968912ffe1150879793ec4ca78c08bae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 28, 2025.
Transparency logSecurity for schemastore 0.2.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for schemastore-0.2.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 28, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
