openwright-s3
An S3 checkpoint store with Object-Lock / WORM retention for OpenWright — tamper-proof chain-of-custody for signed tree heads.
pip install openwright openwright-s3
openwright collector --key key.pem --checkpoint-interval 300 \
--checkpoint-store "s3://my-bucket/checkpoints?lock=COMPLIANCE&days=180"
lock ∈ {COMPLIANCE, GOVERNANCE}; days is the retention window. Under
COMPLIANCE, once a checkpoint is written it cannot be overwritten or deleted
until retention expires — enforced by S3 from the object-lock metadata the store
sets, not by a comment. The bucket must have Object Lock enabled at creation
(S3CheckpointStore.create_locked_bucket). Wraps core's S3CheckpointStore; no
crypto is reimplemented here.
1 maintainer
Metadata
1 maintainer
Release files for openwright-s3 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_s3-0.4.0.tar.gz | 2.6 kB | With provenance | Details for openwright_s3-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openwright_s3-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for openwright_s3-0.4.0-py3-none-any.whl |
Total release size: 5.2 kB
Release files / openwright_s3-0.4.0.tar.gz
| Download URL | openwright_s3-0.4.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10354243e575bee1aea98b2f9db87571a4e82ecd3ef94c04c161aa493ff52d0f
|
|
BLAKE2b-256 checksum How to use checksums |
0af179c69ffae9e8e338cf893703342b03228b89e54bd3c47d3846fa353e1ad9
|
| 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_s3-0.4.0-py3-none-any.whl
| Download URL | openwright_s3-0.4.0-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f68b0422fff0f0bb5fbb3fcbad656773aadd311da1133cd4d48907f80a09ca0f
|
|
BLAKE2b-256 checksum How to use checksums |
60afbea915477172944e9881768000efc7452cf2f5ece19358062101bb9aa9f4
|
| 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-s3 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_s3-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.
