Cryptographic migration planning and post-quantum transition tooling.
Maintained by Lattix Technologies Corp.
Project website: https://lattix.io
This project is an unpublished development workspace with versioned Rust contracts for inventory, cryptographic dependency topology, risk, target profiles, product capabilities, conservative peer compatibility, and advisory source-attributed SCC remediation actions, bounded review-only migration waves and immutable source-pinned plan drafts with unverified exception records. It generates immutable advisory MigrationPlan drafts and independently versioned neutral inventory/ChangeSet/policy fixture contracts; it does not authenticate protocol/PKI proofs or authorize migrations. No public crates.io release is authorized.
- cryptoshift — offline evidence-bound analysis library (unpublished)
cargo run -p cryptoshift --example capability_catalog --locked
cargo run -p cryptoshift --example peer_compatibility --locked
cargo run -p cryptoshift --example remediation_actions --locked
cargo run -p cryptoshift --example wave_plan --locked
cargo run -p cryptoshift --example migration_plan --locked
cargo run --offline --manifest-path acceptance/neutral-consumer/Cargo.toml
See the peer compatibility contract and remediation action contract for evidence and authorization limitations. See the candidate wave planning contract for SCC capacity and review-only states. The immutable migration plan contract describes source digests, risk and exception authority limits. The neutral adapter contract defines the bounded Cryptoshift-owned fixture boundary and explicitly does not claim a released upstream Cryptomap/Cryptopolicy wire integration.
The Gate E2 conformance corpus exercises a versioned synthetic enterprise estate, public end-to-end pipeline, hostile fixtures, seeded determinism and Windows/Linux replay. It does not validate native upstream transports or grant deployment authority. The FOSS-450 atomic analysis API composes existing offline phase contracts into one all-or-nothing advisory result with typed status diagnostics and opt-in aggregate-only metrics. It does not authenticate source claims or authorize migration. Reproducible phase scaling and benchmark methodology is available for synthetic graph, SCC, risk, peer compatibility, remediation, advisory wave and plan workloads. The benchmark never approves cryptographic migrations and gates semantic identity rather than wall-clock performance.
The Getting Started guide documents the v1 public API, full inventory-to-advisory-plan example and the isolated offline Cargo consumer that validates the actual unpublished .crate archive, including Rust 1.85. Plan outputs never confer migration authority. The package remains marked publish = false.
cargo fmt --all -- --check
cargo check --workspace --all-targets --all-features --locked
cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
cargo test --workspace --all-features --locked
The FOSS-456 release assurance procedure describes a manual, no-publish candidate workflow with full main ruleset/check-run verification, SPDX inventory, source-bound provenance metadata and an independent GitHub artifact attestation. It cannot run successfully until FOSS-509 administration and all required CI gates are satisfied. A separate explicit approval is required before any registry release.
All workspace crate manifests explicitly declare publish = false. Release-plz
is manual, release-PR preparation only, with an explicit confirmation input
and only from main. Neither the workflow nor normal pushes publish packages
or receive crates.io publishing credentials.
Run the safety and negative regression checks using Python 3.11+ and Rust:
python3 scripts/release_safety.py --with-cargo
python3 -m unittest discover -s scripts -p "test_release_safety.py" -v
cargo package --locked --list -p cryptoshift
The package listing is a non-publishing inspection, not a publication test.
Before a future release, FOSS-456 must define controlled publishing with appropriate environment approvals, validate package ownership on crates.io, complete API and documentation, MSRV and clean-room consumer verification, security scans, SBOM and provenance, and deliberately change both the manifest and release guard in a reviewed release PR. No release is authorized by FOSS-414.
Repository-local configuration checks do not substitute for administrative branch protections or protected GitHub environments.
Licensed under Apache-2.0 or MIT, at your option.