Dockflow Core
Domain-independent primitives shared by Dockflow CLI, Pipelines and Artifacts: SQLite/PostgreSQL adapters, caller-defined schema initialization/versioning, generic locks, common errors, portable JSON encoding, stream hashing and durable filesystem operations. Core imports no consuming package and owns no domain schema, models, queries or persistence policy.
Install dockflow-core==0.3.0, or dockflow-core[postgresql]==0.3.0 for
PostgreSQL support. The SQLite implementation uses the Python standard library.
Optional drivers and connections are initialized only by explicit operations.
Consumers supply Schema definitions and retain their own queries and policies.
Several independently versioned schemas can share one physical database.
This package follows the shared Dockflow application version and MIT license. Development includes AI assistance. See the repository documentation for configuration and deployment requirements.
1 maintainer
Metadata
1 maintainer
Release files for dockflow-core 0.3.0
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 |
|---|---|---|---|---|
| dockflow_core-0.3.0.tar.gz | 9.5 kB | With provenance | Details for dockflow_core-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dockflow_core-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for dockflow_core-0.3.0-py3-none-any.whl |
Total release size: 22.6 kB
Release files / dockflow_core-0.3.0.tar.gz
| Download URL | dockflow_core-0.3.0.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b57387e774691a72a5aa35a0b8554a708472d2a0a0e4b3f8566f1b54a1838188
|
|
BLAKE2b-256 checksum How to use checksums |
9da0d1926ed48e26e90e34ef561dff95812a6bf823977a9f500caa02f5401d46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 26, 2026.
Transparency logRelease files / dockflow_core-0.3.0-py3-none-any.whl
| Download URL | dockflow_core-0.3.0-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
891e372821b7d50427c1648401e0ad801925ac207afcd719bf7c229ea0fb9f1c
|
|
BLAKE2b-256 checksum How to use checksums |
bfd4d19c09b95cfa8f6fe483a4b96c25508696d06cec0b9f15573b2a6b1ac38e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 26, 2026.
Transparency logSecurity for dockflow-core 0.3.0
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 dockflow_core-0.3.0.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 Oct 26, 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.
