openwright-postgres
A durable, multi-writer PostgreSQL ledger backend for OpenWright — the production answer to the file/sqlite single-writer limit.
pip install openwright openwright-postgres
openwright collector --ledger-backend "postgresql://user:pw@host:5432/evidence"
Or in code:
from openwright.connectors import resolve_backend
from openwright.ledger import Ledger
ledger = Ledger(resolve_backend("openwright.ledger_backends", "postgresql://…"))
It uses core's append-only SqlLedgerBackend (DB-assigned IDENTITY column — no
MAX(idx)+1 race, O(1)+indexed positional reads), so concurrent writers commit
gap-free, ordered, and verifiable. Crypto stays in core; this package only wires
storage. Produces evidence that controls were exercised — not a legal compliance
certification.
1 maintainer
Metadata
1 maintainer
Release files for openwright-postgres 0.4.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 |
|---|---|---|---|---|
| openwright_postgres-0.4.0.tar.gz | 3.2 kB | With provenance | Details for openwright_postgres-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openwright_postgres-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for openwright_postgres-0.4.0-py3-none-any.whl |
Total release size: 5.8 kB
Release files / openwright_postgres-0.4.0.tar.gz
| Download URL | openwright_postgres-0.4.0.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3c4ef6aef62b0ef0ba6019518c5ec3299a9088a80f38e1a4c50a729e08a8ba7
|
|
BLAKE2b-256 checksum How to use checksums |
14ee0debc3ab6297f15ee8dee67648c670605ba5ba019203b7fde95a5368540f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 4, 2026.
Transparency logRelease files / openwright_postgres-0.4.0-py3-none-any.whl
| Download URL | openwright_postgres-0.4.0-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46bbdaa53b101470846acf0bdad497e5aa7549528f2338bcc59c0401f2888c93
|
|
BLAKE2b-256 checksum How to use checksums |
39d727c4a79cef6a1384bbec26611d78ada82c4a8b5f91b3ab601b5e3dab500b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 4, 2026.
Transparency logSecurity for openwright-postgres 0.4.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 openwright_postgres-0.4.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 Jun 4, 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.
