Editorial method
How Reviews Work
Explain recommendation, testing, evidence, approval, freshness, and delisting without presenting a numeric score.
Recommendation is earned through documented review
Open1320 is not a neutral link directory. An active Project appears in the normal reviewed directory only after Open1320 has completed a hands-on review and decided that it can recommend the Project to an appropriate audience.
What the review records
A review can document installation, launch behavior, accounts, data practices, update mechanisms, network observations, source availability, known concerns, unresolved questions, tested versions, file hashes, and the limits of what was tested.
No numerical scores
Open1320 uses a written recommendation and evidence record instead of a score. Important limitations and serious concerns remain visible rather than being hidden behind a number.
Independent approval and factual review
Project owners may correct factual errors before publication, but they do not control the verdict. A Project owner or representative cannot be the only final approver of their own Project.
Review history stays public
Each completed review remains a separate dated record. New reviews do not erase prior findings. The Project page presents the current review and a chronological public history.
Freshness guidance
The routine target is four months. A review can become due or overdue, but a date alone never automatically delists a Project. Major releases, new installers, account changes, updaters, or infrastructure changes can trigger an earlier review.