Editorial policy

We read the repository, not the press release.

Every claim on this site should be traceable to a file we can link to. Here is the exact method behind that, and the places where it stops being good enough.

What we actually do

When a project claims to replace a piece of software people pay for, the interesting question is not whether it looks like the original. It is what is implemented. So for each project we work through four artefacts, in this order:

  1. The README. It states the licence, the platforms, the install path, and — in the better projects — a "status" line that says how finished it is. That status line is the single most useful sentence in the repository, and it is usually the one a press article leaves out.
  2. The source tree. Directory names, crate dependencies and file sizes tell you what is real before any feature list does. A file-format importer that is 300 lines long does not open your files; it opens a subset of them.
  3. The issue tracker. Open issues are a public list of what does not work, written by the people who tried. A project with more open issues than stars is telling you something specific.
  4. The roadmap, if there is one. What the authors have queued but not built is the honest gap between the pitch and the product.

What we do not do

We do not compile these projects, run them on our machines, or benchmark them. Anyone who tells you a review is "hands-on" is claiming a lab they may not have. We would rather be explicit: this site is a source-level review, not a product test.

That limits us in ways worth naming:

How claims are marked

Three marks do the work on every page:

Documented
The repository says so, in a file we link. We are quoting, not vouching.
Confirmed
Two independent artefacts agree — usually README plus source, or README plus an open issue that contradicts it.
Unverified
Plausible, unproven, and labelled. We never silently upgrade one of these to fact.

Dates and versions

Software in this category changes weekly. Every project page carries the date we read it and the commit or release we read. If a page is more than a month old and the project has shipped since, assume the page is stale until we say otherwise.

Money

There are no sponsored reviews, no paid placements, and no affiliate links on review pages. If that ever changes, the change will be announced on the page it affects, above the content, not in a footer.

Corrections

If we got something wrong, the correction is published on the same page with the date and what changed. We do not quietly edit a claim and hope nobody notices; the whole value of a site like this is that you can check us.

The standard we hold ourselves to

If a sentence on this site would not survive someone opening the repository and looking, it should not be on this site.