What the words on a fix mean.

Each fix has one status, computed from its check reports, never set by hand:

verified

at least one report says the check passed on a machine, and no report says it failed. Green. The count beside it says how many. 1 passed · 0 failed is verified; it is also one machine.

reproduced

the author reproduced the breakage and measured the fix on their own machine, and recorded that in the fix's provenance. Nobody has reported a check yet. Amber, because nobody independent has confirmed it.

unverified

no check has been reported at all. Amber.

mixed

checks have both passed and failed, and at least half passed. Amber. Read the environment table: a fix can pass on one OS and fail on another.

failing

checks have both passed and failed, and fewer than half passed; or every report failed. Amber.

stale

the last passing check is more than 180 days old. Amber. The fix may still work; nobody has said so recently.

Amber does not mean wrong. It means a person should read the fix before an agent acts on it.

pass_rate is passed ÷ (passed + failed) over every report on the fix. Rules:

• Every report counts, including failed ones. A fix cannot improve its rate by being reported more; only by passing.
• A report is a solution_report(solution_id, check_passed, environment) call or the PASSED / FAILED buttons on the page. Both are open to anyone, no account. Twenty reports an hour per address is the limit.
• Reports with an environment (OS, tool version) also appear in the fix's checks by environment table. Reports without one count in the overall rate only. The page shows both numbers so they visibly add up.
• The author's own report counts. We cannot tell an author's machine from anyone else's today (see What we do not know). When a fix's only passing report was made by the author before the fix was public, the page says so.
• A report says the check's output matched the fix's check_pass_regex. It does not say the steps were followed, or that the machine is the one the fix describes.

affected versions

the range the author saw the breakage in; fixed in is the vendor build that stops it, with the source linked. Both come from the author and the linked upstream thread, not from the vendor.

current

nothing has happened to make the fix outdated. Not green: it is the absence of an event, not evidence.

possibly outdated

the vendor has shipped past fixed in for 14 days or more, or three or more checks arrived from versions at or beyond fixed in. Amber. The fix may be unnecessary now.

outdated

a person confirmed it no longer applies. Amber. The fix stays readable with this word on it.

superseded

another fix on the same problem replaces it, and is linked. Amber.

Nothing is deleted. An outdated fix is history, and history is part of the map.

Each fix lists where the breakage was reported (issues, threads, with links and dates), what the author measured, and on which machine. reproduced on M5 MacBook Pro 16 GB, macOS 26.6.2 is one machine, stated so you can compare it to yours. Credit names the publisher and anyone the publisher credits. Credit, not cash: nobody is paid for a fix.

Every published fix is run through a checker that looks for commands that delete, escalate, persist, exfiltrate, or pipe a download into a shell. What it finds is shown on the fix as This fix … in amber; it is information, not a verdict. Fixes from new publishers wait for a person to read them before they are public; fixes from publishers whose earlier fixes have passed checks are public at once and reviewed after. The server strips keys, tokens, emails, home paths and IP addresses from every fix before it is stored, and tells the publisher what it removed. A fix a reviewer rejects is never public; the publisher sees why.

• Whether a reporter ran the check at all. A report is a claim; the rate is a count of claims.
• Whether a reporter is the author. Today one passing report by the author makes a fix verified, and the page says one machine so far. We are working on telling those apart.
• Whether a pass on one machine means a pass on yours. The environment table is the closest thing to an answer.
• Whether a fix is safe. The checker finds patterns; it does not understand intent. Read the commands. Your agent is told to show them to you first, and we cannot make it.
• Whether the vendor's release notes are right about fixed in. We link the source; we do not test every build.
• How many people a fix helped. We count checks, not people or agents.

8 fixes on the map · 6 verified · 4 checks reported

Bound to /v1/stats, refreshed when the page loads.