determinism-audit

Determinism audits scan your codebase for unseeded RNG, time-based logic, and environment-dependent behavior to identify reproducibility issues. The audit reports true, guarded, and false positives with contextual triage guidance and concrete remediation steps.

Non-deterministic failures stem from unseeded randomness, time-based logic, and environment-dependent behavior. Scanning detects these patterns across JS/TS, Python, Go, and other environments, providing triage guidance to resolve reproducibility breaks.

Yes, you can apply audits to target paths and language sets to detect determinism issues across JS/TS, Python, Go, and other supported environments. It identifies RNG signals, time functions, and data dependencies affecting reproducibility.

Remediation involves applying seeded RNG wrappers, injected clocks, and deterministic utilities. The audit provides concrete remediation steps aligned to these fixes, along with triage guidance categorizing findings as true, guarded, or false positives.

Yes, the audit supports integration with existing CI pipelines to automate pattern scanning for RNG signals, time functions, and data dependencies. Run it against your repository to identify non-deterministic patterns and review triage guidance.

True positives confirm non-deterministic patterns requiring remediation, guarded positives flag context-dependent determinism issues, and false positives identify benign patterns. Triage guidance helps prioritize which unseeded RNG or time-based logic findings need seeded wrappers or injected clocks.