Show HN: ReWeaver AI DriftDetector – score a GitHub repo's production readiness

ReWeaver launched DriftDetector, a tool that scores a GitHub repository's production readiness with a single Production Drift Ratio between 0 and 1, banded from Low to Severe. The tool scores a repository's full commit history to identify which commit introduced drift, reports findings by file and line, and exports results as JSON, PDF, or Markdown. ReWeaver states the scan is rule-based rather than LLM-driven, so it produces identical scores on repeat scans and incurs no per-scan API costs.

What DriftDetector tells you in less than a minute: A single Production Drift Ratio 0–1 , banded from Low to Severe. Two repos, or the same repo six months apart, are actually comparable. Tells you exactly where the code has drifted from intent or standards, line by line, so you don't have to go searching. The full history gets scored, not just today's code — see precisely which commit opened the gap, and whether it's closing or widening. Tells you how many hours the one scan just saved you and how many issues can be auto-fixed coming in ReWeaver versus what needs human judgment. Sample Report View the report on screen or download as JSON, PDF, or Markdown for a full list of drift instances. Below is a sample. Same repo, same score, every time. Every dimension is rule-based, not an LLM's best guess — scan a repo twice and get the same answer twice. Nothing here calls an LLM. No API costs per scan, no context window to run out of — which is exactly why this can stay free instead of metered. Every finding is a file and a line, not a paragraph of AI prose. Click through to GitHub and check it yourself — nothing to take on faith.