How We Rate Software

Every program in the BigForkSteering catalogue carries a star score from one to five. The number reflects the editor’s overall recommendation strength, weighted explicitly across five concrete factors. This page documents what each level means, what we weigh, and what changes a score over time.

The five-star scale

  • 5 stars — Industry-defining. Recommended without hesitation for any user in the program’s scope. The free tier is genuinely complete; format support, stability and ecosystem are best-in-class. Programs at this level are the ones we’d install first on a new machine.
  • 4 stars — Excellent for most users with minor caveats. The free tier is usable for real work; there may be one or two missing features, format gaps or interface frictions that hold it back from a five. Strong default recommendation.
  • 3 stars — Good but specific. The program does its job for a narrow audience or workflow. Larger workflows will outgrow it. Worth knowing about, worth installing in the right circumstance.
  • 2 stars — Functional but limited. Works, but better free alternatives exist in almost every case. Listed for completeness; install only if a specific feature isn’t available elsewhere.
  • 1 star — Skip unless you have a specific reason. The program is included in the catalogue because it meets the four selection criteria, but it does not earn a recommendation. Stale, buggy, watermarked, paywalled at the free tier, or thoroughly outclassed by a stronger alternative.

What we weigh

Five factors drive a score, with the editor’s judgement on how each one plays for the specific program. Weights are not strict percentages — they are how much each factor moves a verdict up or down from the editor’s starting impression of overall quality:

  • Free-tier completeness (≈40% influence) — On a free download, can a real user accomplish a real task without paying? For freemium programs, what is gated and what is open? Is the trial period long enough to learn the tool?
  • Stability and update cadence (≈20%) — Does the program crash? Is it actively maintained? When was the last release? Are security issues patched?
  • UX and documentation (≈15%) — Can a new user produce a usable result on the first day? Is the documentation accurate? Are the official tutorials current?
  • Format / protocol support (≈15%) — Does the program handle the formats and protocols real workflows require? For an archiver, the container coverage (7z, RAR, ZIP, TAR). For a media player, the codec coverage. For an email client, the protocols (IMAP, SMTP, OAuth). For an IDE, the language and framework coverage.
  • Community and ecosystem (≈10%) — Plugins, presets, third-party tutorials, active forums. Does the program have momentum beyond the core developer?

What we do not weigh

Price does not affect the score — every program in the catalogue meets the "freely downloadable" selection criterion already. Marketing claims do not move the needle; we test against actual behaviour, not announcements. Stock screenshots and curated demo files are ignored; we run real source media through the program. Recency of the catalogue entry is irrelevant; an old reliable program can earn five stars and a newly released program can land at two.

When scores change

A verdict changes when the program changes. New major release with substantial features added — re-evaluation. Free tier restricted (export limits introduced, formats removed, watermark added) — re-evaluation, almost always downward. Free tier expanded (paid features moved to free) — re-evaluation, usually upward. Major bug fixed that previously cost stars — re-evaluation. Program abandoned for 24+ months without releases — flagged, likely dropped from the catalogue.

Verification

Ratings are documented on each program’s catalogue page along with the rationale. If you disagree with a rating and can show evidence that contradicts the editorial assessment — a feature we missed, a recent release we haven’t reflected, a bug we underweighted — please contact us. The full review process is documented in editorial methodology, with editorial responsibility resting on Jane Hoskyn.

Common Questions About Software Ratings

What does a 5-star software rating mean on BigForkSteering?

Industry-defining. Recommended without hesitation for any user in the program’s scope. The free tier is genuinely complete; format support, stability and ecosystem are best-in-class. Programs at five stars are the ones we’d install first on a new machine.

What factors do you weigh when rating software?

Five factors: free-tier completeness (around 40% influence), stability and update cadence (around 20%), UX and documentation (around 15%), format and protocol support (around 15%), and community ecosystem (around 10%). Weights are guidelines, not strict percentages — the editor’s judgement on how each factor plays for a specific program drives the final rating.

Does price affect software ratings?

No. Every program in the catalogue already meets the freely downloadable selection criterion, so price is a constant. Marketing claims, stock screenshots, and recency of the catalogue entry also do not affect ratings. We test against actual behaviour on real source media, not press releases.

When does a software rating change?

A rating changes when the program changes. Triggers include a new major release with substantial features added, free tier restricted (export limits, watermarks introduced), free tier expanded (paid features moved to free), major bugs fixed that previously cost stars, or 24+ months without releases (flagged, likely dropped from the catalogue).

Can vendors influence their software’s rating?

No. There is no paid placement, no sponsored ratings, no commercial arrangement that influences ratings. Vendors can submit corrections through the contact form when they have evidence we missed a feature or a recent release, but the editor’s verdict remains independent.

How do you handle disagreements with a software rating?

If you can show evidence that contradicts the editorial assessment — a feature we missed, a recent release we haven’t reflected, a bug we underweighted — use the contact form. We re-evaluate when there’s substantive new information, not when there’s complaint pressure alone.