Editorial policy
What gets published here, how it is measured, and the handful of things no amount of money changes.
Who writes this
One person: Keyoor. There is no editorial team, no contributor network and no sponsored desk. Drafting is assisted by language models; the measurements are not, and every published page is the author’s responsibility regardless of what wrote the first sentence.
Reviews are runs, not readings
A review is not written from a README. Each project is cloned at a specific commit into a throwaway container — non-root, no host access, hard timeouts — where it is installed, built and put through its own test suite. What comes back is what gets published: install time, disk cost, dependency count, how many tests passed, what the audit reported. That is how all 1,449 repository reviews and 992 library guides on this site are produced. The method is written down in full on how we test.
Some projects do not survive that. A build that fails on our machine is reported as a build that failed on our machine — not as a broken project, and not quietly omitted. A project the lab could not run at all says so on its page, and its guide is written from documentation with that limitation stated.
What a score means
Scores are the author’s judgement against a fixed rubric — setup ease, documentation, community health, maturity — informed by the run. They are opinions with evidence attached, not measurements, and the page always shows the evidence so a reader can disagree with the conclusion and still use the numbers.
Corrections
Measurements go stale and sometimes they are wrong. When a number is disputed the project is re-run rather than edited, and the page carries the date of that run. The full policy, and what counts as a correction, is on the corrections page.
Independence
- No payment, sponsorship, affiliate arrangement or equity has ever influenced a review, a score or a placement.
- No project can pay to be reviewed, to be reviewed sooner, or to have a review removed.
- No guest posts, link exchanges or paid backlinks. Requests for them are not answered.
- Where a project is a competitor to something published here, it is said on the page.
If any of that changes — if this site ever takes advertising or affiliate revenue — it will be disclosed here first, on the page, before it appears anywhere else.
Sources
Claims about a project link to the project: its repository, its documentation, its release notes, its issue tracker. Where a claim comes from someone else’s reporting, that reporting is linked. External links are checked weekly and pages whose sources have gone are queued for rewriting rather than left citing a dead URL.
Use of AI
Language models draft prose from the measured facts and the author’s notes; they do not decide verdicts, invent numbers, or write anything that is not backed by the run. Generated text is checked against a budget of machine-writing tells and a quotability floor before it can be published, and anything that fails is rewritten rather than shipped.
Reaching us
Corrections, disputes and review requests all go to the same inbox — see contact. A correction with evidence gets priority over everything else.