This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: Not ready for use
our-compliance
GDPR/PII compliance module for the ourochronos ecosystem.
Features
- Data Deletion: GDPR Article 17 (Right to Erasure) compliant deletion with cryptographic erasure
- PII Scanning: Detect and block PII (emails, phone numbers, SSNs, credit cards, etc.)
- Tombstone Records: Federation-aware deletion propagation with audit trails
Installation
pip install our-compliance
Usage
from our_compliance import delete_user_data, scan_for_pii, DeletionReason
# Scan text for PII
matches = scan_for_pii("Contact me at user@example.com")
# Delete user data with compliance audit trail
await delete_user_data(user_id, reason=DeletionReason.USER_REQUEST)
Development
pip install -e ".[dev]"
ruff check src/ tests/
mypy src/
pytest tests/ -m "not integration"
1 maintainer
Metadata
1 maintainer
Release files for our-compliance 0.1.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 | |
|---|---|---|---|---|
| our_compliance-0.1.0.tar.gz | 15.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| our_compliance-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.4 kB
Release files / our_compliance-0.1.0.tar.gz
| Download URL | our_compliance-0.1.0.tar.gz |
|---|---|
| Size | 15.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6293a0a480098da732ec3f931619283e8161679e127b115feaca7a06724259ad
|
|
BLAKE2b-256 checksum How to use checksums |
a838a0840c1526c297c896c6aee04458f71edcae5be3a5807d054a5aa18e2b47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / our_compliance-0.1.0-py3-none-any.whl
| Download URL | our_compliance-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
05586f78583a9794f9617e353d122d39ffc6bbc72cce119cc9d6efdf4f0153d8
|
|
BLAKE2b-256 checksum How to use checksums |
621c109b22ff2d19e54a25f60957873021ecd71b655353a1b135f8bd80686e62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for our-compliance 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
