Ahrefs Domain Rating set in type 25 Oct 2026, reset 25 Oct 2026.
Refactron™ metrics
Set in type for refactron.dev: Ahrefs Domain Rating and Majestic link data, with the change since the last edition.
Metric
Value
Domain Rating
2● no change since last check
Trust Flow
0● no change since last check
Citation Flow
15● no change since last check
Referring domains
4● no change since last check
External backlinks
9● no change since last check
Ahrefs Domain Rating set in type 25 Oct 2026, reset 25 Oct 2026. Majestic set 25 Oct 2026, reset 25 Oct 2026. Link data typeset by Majestic. Trust Flow, Citation Flow and Topical Trust Flow are trademarks of Majestic-12 Ltd.
Refactron™ domain colophon
From the registry's public RDAP record, checked 25 Oct 2026, 18:09 UTC.
Refactron™ verifies diffs from any source: Cursor, Claude Code, Copilot, Codex, codemods, or manual edits. The MCP server is available today, allowing agents to call verify_change on their own work before landing changes.
Does my code leave my machine?
No. Refactron™ runs locally against your real test suite in an isolated shadow tree. No code is sent to an external service to make the verdict.
How is this different from just running my tests in CI?
CI only tells you the suite passed. Refactron™ checks whether any test actually executed the lines you changed, returning UNPROVEN when the answer is no, so passing tests on untested code no longer appear as proof.
What ships today vs. what's coming?
Shipping today: the CLI (npm install -g refactron) and MCP server with verify_change tool. Changed-line coverage proof works for Python today; TypeScript diffs run all gates but cap at UNPROVEN. In early access: the hosted CI gate.
What does UNPROVEN mean?
Your tests pass, but the changed lines aren't actually exercised by any test, so “green” proves nothing. We say so explicitly and list the tests to add, instead of hand-waving.
Find Refactron™ online
Leave a review for Refactron™
No review of Refactron™ set in type yet. Set the first.