Constant-Time Analysis finds variable-time operations in crypto code written in C, C++, Go, Rust, Swift, Java, Kotlin, C#, PHP, JavaScript, TypeScript, Python or Ruby. A bundled analyzer compiles the file, reads the emitted assembly or bytecode, and flags division and modulo, weak random number use, secret-dependent branches, early-exit comparisons and table lookups.
The compile step is mechanical and the triage is the real work: the analyzer has no data flow analysis, so a failed report is a worklist. The agent must trace each flagged operand back to a key, plaintext or nonce and state a verdict with the data flow behind it.
What You Get
- Analyzer reports per function with severity and the reason an instruction is variable-time
- Language guides listing dangerous instructions and constant-time replacements
- A triage method that separates true positives from public-length divisions
- A table of constant-time comparison primitives for each language
Common Use Cases
- Reviewing a signature, KEM or key derivation routine for KyberSlash-style division on secrets
- Checking whether a MAC or tag comparison exits early
- Re-checking a fix across compilers, targets and every optimization level
- Sweeping a crypto source directory file by file
What Makes It Unique
It treats the tool output as a worklist and spends most of its text on triage, with known-answer samples per language that pair a true positive with an identical-looking false positive. It also requires results to name the compiler, architecture and optimization level, since a clean run proves one configuration only.
Under The Hood
The skill loads an instruction file and language reference guides, then runs a bundled Python analyzer through uv on one file at a time. The analyzer invokes the local toolchain for the language, such as gcc, clang, go, rustc, swiftc, javac, node, php or ruby, to compile or dump bytecode, and reads the result. Compilation writes build outputs on your machine, and the analyzer may use cross compilers you name. It never executes the code under test, and it does not fetch web pages or call APIs.