Reach the desk
Corrections, tips, and review requests all land in the same inbox.
mrkeyoor@gmail.com — read daily. For corrections, include the page URL and the claim in question; fixes are stamped with an updated date on the affected page.
Social
DMs are open on X (@mrkeyoor).
Review requests
Want an open-source project evaluated? Send the repo URL. Every review follows the same public rubric — see how the reviews are made. Scores cannot be bought, and there is no paid placement.
What happens to your message
One person reads this inbox: Keyoor. There is no support team and no ticket number. Corrections are the priority and usually go live the same day; review requests are queued and answered only if the project is actually going to be run. Everything else may not get a reply, which is a limit worth stating rather than pretending otherwise.
Corrections policy
Every review on this site is built from a real run — the project is cloned into a clean container, installed, built and tested, and the numbers on the page are whatever came back. That means a number can be wrong for honest reasons: a flaky test, a version that moved, a machine-specific failure. If you can show a measurement is wrong, say what you ran and what you got. The page is re-run rather than quietly edited, and it carries an updated date afterwards. Verdicts change when the evidence changes.
What we will not do
- Remove a low score, or a “who it is not for” section, on request.
- Accept payment, sponsorship, affiliate terms or equity for a review or a placement.
- Publish a review of a project we could not run ourselves without saying so on the page.
- Add or sell backlinks, guest posts, or “collaboration” articles.
Press and licensing
Quoting our measurements is welcome — cite the page and the date, because the numbers are re-measured and they move. For a bulk feed of the review data rather than scraping, ask; that is what the should-i-use MCP server exists for.