pqblocks-cnsa-evidence
CNSA 2.0 Procurement Evidence Pack Generator for federal contractors and enterprise systems transitioning to post-quantum cryptography.
pqblocks-cnsa-evidence parses cryptographic bill of materials (CBOM) scan results and multi-ecosystem build lockfiles to synthesize a formal, audit-ready evidence pack meeting US National Security Agency (NSA) Commercial National Security Algorithm Suite 2.0 (CNSA 2.0) compliance requirements.
Key Features
- Multi-Ecosystem Lockfile Ingestion: Native parsing for Python (
requirements.txt,setup.py,pyproject.toml), Go (go.mod), JavaScript (package-lock.json), and Java (pom.xml). - CycloneDX 1.6 CBOM Synthesis: Generates schema-valid CycloneDX 1.6 software and cryptographic bills of materials enriched with post-quantum properties.
- CNSA 2.0 Compliance Matrix: Automatically classifies algorithms against CNSA 2.0 timelines (A through F grading) based on NIST IR 8413 projections.
- Automated Migration Scheduling: Computes phased migration roadmaps, component-level replacement milestones, and milestone timelines.
- Cryptographic Attestation: Issues SHA-256 integrity attestations binding all generated reports (SBOM, crypto inventory, compliance matrix, migration plan, narrative, and source lockfiles).
Installation
pip install pqblocks-cnsa-evidence
Dependencies
pqblocks-cnsa-evidence is a pure-Python document generation and compliance engine requiring cryptography, pyyaml, and toml.
Quickstart
import hashlib
import json
from pqblocks_cnsa_evidence import (
scan_parser,
lockfile_parser,
sbom_emitter,
crypto_inventory_emitter,
compliance_matrix_emitter,
narrative_emitter,
migration_scheduler,
executive_summary_emitter,
attestation_emitter,
)
# 1. Ingest scan findings and lockfile
scan_data = {
"algorithms": [
{"name": "ML-KEM-1024", "type": "key-encapsulation", "mode": "PQC", "keySize": 1024, "cnsA20Grade": "A", "breakYear": 2040},
{"name": "RSA-2048", "type": "signature", "mode": "classical", "keySize": 2048, "cnsA20Grade": "D", "breakYear": 2030},
{"name": "AES-256", "type": "encryption", "mode": "classical", "keySize": 256, "cnsA20Grade": "A", "breakYear": 2050},
],
"tls_endpoints": [{"host": "api.fed.gov", "cipher": "TLS_AES_256_GCM_SHA384"}],
"dependencies": [{"name": "cryptography", "version": "42.0.5"}],
"pqc_grades": {"ML-KEM-1024": "A", "RSA-2048": "D", "AES-256": "A"}
}
lockfile_content = "cryptography==42.0.5\nrequests>=2.31.0\n"
scan_res = scan_parser(scan_data)
lock_res = lockfile_parser("python", lockfile_content)
# 2. Synthesize evidence pack components
sbom = sbom_emitter(scan_res, lock_res)
inventory = crypto_inventory_emitter(scan_res, lock_res)
matrix = compliance_matrix_emitter(scan_res)
narrative = narrative_emitter(scan_res, lock_res)
schedule = migration_scheduler(lock_res, matrix)
exec_summary = executive_summary_emitter(matrix, narrative, schedule)
def sha256(val):
b = val.encode("utf-8") if isinstance(val, str) else json.dumps(val, sort_keys=True).encode("utf-8")
return hashlib.sha256(b).hexdigest()
# 3. Create cryptographic attestation
attestation = attestation_emitter(
sbom_sha256=sha256(sbom),
inventory_sha256=sha256(inventory),
narrative_sha256=sha256(narrative),
compliance_sha256=sha256(matrix),
migration_plan_sha256=sha256(schedule),
executive_summary_sha256=sha256(exec_summary),
tool_version="0.1.0",
tool_timestamp="2026-10-26T00:00:00Z",
scan_json_sha256=sha256(scan_data),
lockfile_hashes={"requirements.txt": sha256(lockfile_content)},
)
print(f"Evidence Pack Generated: {sbom['bomFormat']} {sbom['specVersion']}")
print(f"Compliance Status: {matrix.get('status', 'complete')}")
Evidence Pack Architecture
evidence-pack/
├── sbom.json # CycloneDX 1.6 CBOM with post-quantum properties
├── crypto-inventory.json # Structured algorithm and key-size catalog
├── compliance-matrix.json # CNSA 2.0 requirement evaluation and grading
├── migration-plan.yaml # Phased timeline and dependency upgrade schedule
├── narrative.md # Key-management narrative (5 mandatory sections)
├── executive-summary.md # Decision-maker brief with risk analysis
└── attestation.json # SHA-256 manifest cryptographically sealing the pack
Non-Claims & Compliance Notice
License
This project is licensed under the Apache 2.0 License. See LICENSE and NOTICE for details.
Metadata
Release files for pqblocks-cnsa-evidence 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 |
|---|---|---|---|---|
| pqblocks_cnsa_evidence-0.1.0.tar.gz | 43.1 kB | Without provenance | Details for pqblocks_cnsa_evidence-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pqblocks_cnsa_evidence-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for pqblocks_cnsa_evidence-0.1.0-py3-none-any.whl |
Total release size: 65.4 kB
Release files / pqblocks_cnsa_evidence-0.1.0.tar.gz
| Download URL | pqblocks_cnsa_evidence-0.1.0.tar.gz |
|---|---|
| Size | 43.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ddf70c4f1ab3aa69451ff475fa048f84046caab66f766b355bd108bfbf480792
|
|
BLAKE2b-256 checksum How to use checksums |
f1f548d645372497048af4c5c6b37420c58149c2866e7d335ac7b02d153dc360
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / pqblocks_cnsa_evidence-0.1.0-py3-none-any.whl
| Download URL | pqblocks_cnsa_evidence-0.1.0-py3-none-any.whl |
|---|---|
| Size | 22.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8d3ad2e694cc719d12b6288a7cd49280f0e9ba70f68e360de84a8a133995a79
|
|
BLAKE2b-256 checksum How to use checksums |
920294cf29a37400927b3e0156de7630114df8761ceae26dbb05667675d31e90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for pqblocks-cnsa-evidence 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.