httk-store
⚠️ EARLY BETA
This is an early beta release of httk₂. The organization of the packages and their APIs should not yet be regarded as stable, and may change between releases.
httk-store is a httk₂ module for data
management. Built on the stdlib-only contracts and models in httk-core, it
provides in-memory httk.core.EntryProvider implementations for the standard
OPTIMADE entry types (references, files, calculations),
property-definition validation on jsonschema, and a database storage layer
that stores plain frozen dataclasses in SQLite, DuckDB, PostgreSQL, or MongoDB,
makes them queryable through a backend-agnostic search DSL, and serves them
through the entry-provider contract. ClickHouse supports bulk ingestion and
read serving with its documented write restrictions.
Install the optional backend you need with httk-store[db] (SQLite),
httk-store[duckdb], httk-store[postgresql], httk-store[mongodb], or
httk-store[clickhouse,parallel]. See the
storage documentation for backend
capabilities and deployment requirements.
Metadata
Release files for httk-store 2.1.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 |
|---|---|---|---|---|
| httk_store-2.1.3.tar.gz | 754.7 kB | With provenance | Details for httk_store-2.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| httk_store-2.1.3-py3-none-any.whl | Python 3 | none | any | Details for httk_store-2.1.3-py3-none-any.whl |
Total release size: 1.3 MB
Release files / httk_store-2.1.3.tar.gz
| Download URL | httk_store-2.1.3.tar.gz |
|---|---|
| Size | 754.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e94dbf4e030e635385f17ead0505a4db7f03aece7a0105f460a72bf0922e61eb
|
|
BLAKE2b-256 checksum How to use checksums |
b039a31e3e81f388c3482dde575a5f91ff0fd4e7424aafd83051968256bc4fef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Sep 18, 2026.
Transparency logRelease files / httk_store-2.1.3-py3-none-any.whl
| Download URL | httk_store-2.1.3-py3-none-any.whl |
|---|---|
| Size | 495.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3edeb0f887159cea5c794989a401900eb589be8a50f06f0e666d2604bc1f3583
|
|
BLAKE2b-256 checksum How to use checksums |
639a7fd2bbac89b6625e677b766616464f6211073c890dc7ad3a7cc7bb75bed3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Sep 18, 2026.
Transparency logSecurity for httk-store 2.1.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for httk_store-2.1.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 Sep 18, 2026.
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.