compliance-checkkit
compliance-checkkit is a small Python library and CLI for defining compliance
controls, attaching evidence, and producing simple pass/fail reports.
It is designed for early audit automation, internal readiness checks, and CI gatekeeping where a lightweight checklist is enough.
Install
pip install compliance-checkkit
For local development:
python -m pip install -e ".[dev]"
Quick Start
Create a checklist:
id: soc2-lite
name: SOC 2 Readiness
controls:
- id: access-review
title: Quarterly access reviews are completed
required: true
checks:
- evidence_key: access_review_completed
equals: true
- id: incident-plan
title: Incident response plan exists
required: true
checks:
- evidence_key: incident_response_plan_url
present: true
Create evidence:
{
"access_review_completed": true,
"incident_response_plan_url": "https://example.com/plan"
}
Run the CLI:
compliance-checkkit evaluate checklist.yml evidence.json
Use the library:
from compliance_checkkit import evaluate_files
report = evaluate_files("checklist.yml", "evidence.json")
print(report.summary.status)
Checklist Format
Each control contains one or more checks. A control passes only when all of its checks pass.
Supported check fields:
evidence_key: key to read from the evidence filepresent: true: value must be present and non-emptyequals: value must equal the expected valuecontains: value must contain the expected item or substringone_of: value must be one of the listed values
Publish
Update the package metadata in pyproject.toml, especially the GitHub URLs, then:
python -m pip install -e ".[dev]"
python -m pytest
python -m build
python -m twine upload dist/*
For a safer first release, publish to TestPyPI:
python -m twine upload --repository testpypi dist/*
License
MIT
Metadata
Release files for compliance-checkkit 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 | Actions |
|---|---|---|---|---|
| compliance_checkkit-0.1.0.tar.gz | 6.5 kB | Without provenance | Details for compliance_checkkit-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| compliance_checkkit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for compliance_checkkit-0.1.0-py3-none-any.whl |
Total release size: 14.3 kB
Release files / compliance_checkkit-0.1.0.tar.gz
| Download URL | compliance_checkkit-0.1.0.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1a063fa014fecb085e60071c3933e027b0049c9c00b85c8031f79cfcd268348
|
|
BLAKE2b-256 checksum How to use checksums |
1482008ac734e6be3dcc03cfe3c1ddb674d98dce628abcd5716ac9c052b6097f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Release files / compliance_checkkit-0.1.0-py3-none-any.whl
| Download URL | compliance_checkkit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fe2167f243bdef6c52f2b6def606b6db99dbbe72273b755fc34e5881a94a121d
|
|
BLAKE2b-256 checksum How to use checksums |
169f17f83216874b57574f3a5f5209a2821c444ee3e4eabe4204841f6a241c12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Security for compliance-checkkit 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.