constant-time-testing

Measures timing side channels in cryptographic implementations by running them, using dudect for statistical analysis and Timecop over Valgrind for dynamic tracing. Covers the formal, symbolic, dynamic, and statistical tool categories and how to read a result. Use when testing whether a running implementation is constant-time, measuring timing variance on a compiled binary, or investigating a suspected timing attack. Not for statically inspecting compiler output — the constant-time-analysis plug

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• rea-analysis-optimization 456,653 ★
  Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserv
• rea-ci-tests-audit 456,653 ★
  Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for s
• diagnosing-bugs 323,485 ★
  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or r
• migrate-to-shoehorn 323,485 ★
  Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, w
• webapp-testing 193,970 ★
  Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend