Find cryptography across the codebase.
Identify cryptographic calls, libraries, dependencies, configurations, and weak or quantum-vulnerable patterns.
Cryptographic posture management built for the migration era
Know your cryptography.
Change it with evidence.
Ciphertron scans the cryptography inside your repositories, traces how it is used, and turns the result into a prioritized CBOM—so migration decisions can start with evidence.
01
Discover assets
02
Trace usage
03
Prioritize change
04
Retain evidence
CT / Repository reviewSource remains controlledPublic GitHub
CT
Repository workspace
Connect a repository.
Start from a GitHub URL. Repository access and source handling are confirmed in the Ciphertron workspace.
InventoryCryptographic assets
TraceCross-file usage
PrioritizeMigration register
ExportCycloneDX CBOM
CycloneDX 1.6 CBOMCross-file traceIsolated verificationRetained evidence
Repository reviews remain bounded to the source and evidence needed for the decision.
Structured outputCycloneDX 1.6 CBOM
Cross-file contextCross-file trace
Controlled accessIsolated verification
Retained recordRetained evidence
01 / System of recordOne system of recordScan your repo.
One system of recordScan your repo.
Get your CBOM.
Start with source context, not a generic dependency list. Ciphertron identifies cryptographic assets, traces how they are used, and structures the result for engineering and risk teams.
⌘
Example repositoryacme/payments-api
Inspecting stage 1 of 4
RSA-OAEP
A quantum-vulnerable key-transport path is present in the authentication boundary.
12 assetsIllustrative output
auth/token.ts:84Illustrative interface. Connect your own repository after access is provisioned.
Structured output
A prioritized migration register.
Every detected asset stays connected to its location, use, and suggested migration state.
CT-001RSA-OAEP
auth/token.tsReview requiredCT-002AES-CBC
vault/envelope.goReplaceCT-003SHA-1
signing/receipt.pyReplaceCT-004ECDSA P-256
audit/chain.rsTrace context12 assets mapped31 paths traced8 actions prioritized
Illustrative product data.
02 / Evidence trail
Context survives the handoffFrom source to a reviewable decision.
Inventory alone cannot direct a migration. Ciphertron keeps discovery, context, priority, and evidence connected.
Trace the path, not just the line.
Connect assets to cross-file usage, data paths, dependencies, and the system boundaries that determine impact.
Keep the decision reviewable.
Carry the finding, migration state, supported verification result, and human review into one retained record.
Finding→Usage context→Priority→Human review→Record
03 / Enterprise readiness
Control stays visibleBuilt for sensitive source and accountable change.
Ciphertron is designed to limit source handling, isolate supported verification work, and preserve a reviewable record.
Controlled source handling
Hosted scans use a temporary workspace designed to be cleaned after processing.
Isolated verification
Supported migration checks can run with network access removed and container capabilities restricted.
Structured output
CycloneDX 1.6 CBOM data turns repository findings into a portable, reviewable inventory.
Human-controlled change
Evidence supports engineering judgment. Review remains part of the decision before code changes land.
Repository context is used to produce a structured posture record. Internal orchestration and proprietary evaluation logic remain outside the customer-facing surface.
Evidence supports judgment. It does not replace it.- What is Ciphertron?
- A repository-native system for finding cryptography, understanding its use, and retaining the evidence needed to change it.
- What is a CBOM?
- A cryptography bill of materials: a structured inventory of cryptographic assets, locations, uses, and migration state.
- Does this page receive source code?
- No. Repository review continues in the Ciphertron workspace, where access and source handling are confirmed separately.