This page tracks previously declined entries that may deserve another look.
Use this page for items that were not accepted at the time of review, but may become eligible later after fixes, updates, proof, or stronger documentation.
This page exists so the curation process stays strict without becoming permanently closed-off.
Related pages:
An item should go here when it was declined for a fixable reason, such as:
- missing screenshots or demo material
- weak or incomplete documentation
- unclear install/download path
- unclear licensing/free status
- early-stage project that later became usable
- inactive-looking project that received meaningful updates
- presentation not strong enough at the time of first review
Items that were removed for fraud, malicious behavior, obvious spam, or hard disqualifying reasons should go to BANNED.md, not here.
To be reconsidered, an entry should usually show one or more of the following:
- clearer description of what it is
- real screenshots or product visuals
- working website/repo/download page
- transparent pricing or free license status
- better docs or setup instructions
- proof of actual usability
- stronger trust signals from the author/team
- meaningful development activity or release updates
Add items below once they have enough reason to revisit.
- Original Status: Declined
- Why It Was Declined: Short summary
- What Changed: Short summary of improvements
- Why Reevaluation Makes Sense: Short explanation
- Issue / Discussion Reference:
# - Priority: Low / Medium / High
- Decision After Reevaluation: Pending / Approved / Declined Again
- Confirm the original decline reason.
- Check whether the specific problems were actually fixed.
- Reassess fit, trust, quality, and usefulness.
- Approve, keep declined, or move to banned if new disqualifying issues are found.
- Reevaluation is not guaranteed approval.
- The burden is on the entry to show clear improvement.
- This page helps keep the repo fair, transparent, and high-signal.