certificate-manipulation
Consolidate, split, filter certificates.
Input formats currently supported:
- PEM/CRT (
.pem,.crt) - DER/CER (
.der,.cer) - PKCS7 bundles (
.p7b,.p7c)
Quickstart
uv sync --group dev
uv run pre-commit install
uv run ruff format .
uv run ruff check .
uv run ty check src tests
uv run pytest
uv run pre-commit run --all-files
CLI Usage
uv tool run certificate-manipulation --help
uv tool run certificate-manipulation combine --inputs ./a.crt ./b.pem --output ./bundle.pem
uv tool run certificate-manipulation combine --inputs ./a.crt ./b.der ./chain.p7b --output ./bundle.pem
uv tool run certificate-manipulation split --input ./bundle.pem --output-dir ./out --ext crt
uv tool run certificate-manipulation convert --input ./a.crt --output ./a.pem --to pem
uv tool run certificate-manipulation filter --input ./bundle.pem --output ./filtered.pem --subject-cn router
uv tool run certificate-manipulation filter --input ./bundle.pem --output ./active.pem --exclude-expired
uv tool run certificate-manipulation filter --input ./bundle.pem --output ./regex.pem --subject-cn-regex "^router-.*"
uv tool run certificate-manipulation filter --input ./bundle.pem --output ./or.pem --subject-cn router --issuer-cn corp-root --logic or
uv tool run certificate-manipulation combine --inputs ./a.crt ./b.crt --output ./bundle.pem --report-json ./combine-report.json
Benchmark
Run a basic performance check on a generated large bundle:
uv run python scripts/benchmark_large_bundle.py --cert-count 500
uv run python scripts/benchmark_large_bundle.py --cert-count 500 --clean --workdir .benchmarks/local --output-json .benchmarks/local/report.json --thresholds-file benchmarks/ci_thresholds.json
The script prints JSON timings for combine, split, and filter.
If the workdir already exists, rerun with --clean.
CLI Exit Codes (certificate-manipulation)
0: Success1: Validation error2: Runtime/parse error3: Partial success (--on-invalid skipwith rejected certificates)
Benchmark Script Exit Codes (scripts/benchmark_large_bundle.py)
0: Benchmark completed and all configured thresholds passed2: At least one benchmark timing exceeded configured thresholds
Troubleshooting
No PEM certificates found: ensure files contain-----BEGIN CERTIFICATE-----/-----END CERTIFICATE-----blocks.- Exit code
3: operation completed with--on-invalid skip, at least one invalid cert was ignored. No valid certificates found: input exists but contains no parsable X.509 PEM certificates.No certificates matched filter criteria: input is valid but your filter is too restrictive.- Existing output path collisions: default
--overwrite versionwritesname.v2.ext,name.v3.ext, etc.
Project Layout
src/certificate_manipulation: package codetests/unit: fast default teststests/integration: component-level teststests/end2end: user-facing behavior testsdocs/engineering/CONTRACTS.md: frozen public CLI/API contractsdocs/engineering/RELEASE_RUNBOOK.md: hardened release processCHANGELOG.md: formal release historyskills: AI helper skills for coding workflows
Release
Follow docs/engineering/RELEASE_RUNBOOK.md.
At minimum:
- Bump version in
pyproject.tomlandsrc/certificate_manipulation/__init__.py. - Cut release notes from
CHANGELOG.md(Unreleased->X.Y.Zsection). - Build and verify artifacts (
python -m build,twine check dist/*). - Create and push git tag
vX.Y.Z. - Let GitHub Action publish.
For manual validation, use workflow dispatch with publish_target=testpypi.
Metadata
Release files for certificate-manipulation 1.0.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 | |
|---|---|---|---|
| certificate_manipulation-1.0.0.tar.gz | 19.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| certificate_manipulation-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 42.6 kB
Release files / certificate_manipulation-1.0.0.tar.gz
| Download URL | certificate_manipulation-1.0.0.tar.gz |
|---|---|
| Size | 19.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
35f224c991636c410da4cdd6603385b1ce2bd17d38034cce4ef45cdce7403008
|
|
BLAKE2b-256 checksum How to use checksums |
8b98141a38fa26cb30cb5555e8bd14f461252e2cf5bd60cb5009bff099d2038a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 21, 2026.
Transparency logRelease files / certificate_manipulation-1.0.0-py3-none-any.whl
| Download URL | certificate_manipulation-1.0.0-py3-none-any.whl |
|---|---|
| Size | 23.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d6c837b845a43adab2988263136afd8fb874daa4da55b0ad8e3d6493cb06a429
|
|
BLAKE2b-256 checksum How to use checksums |
0e3c42bea977d7f0e931361c6ef236532de12c4e303c1575f473bbc475cbfd2f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 21, 2026.
Transparency log