How we pick
Our selection and honesty policy: what a repo needs to make the cut, what each label means, and what we will not do.
What a repo needs to make the cut
- Free and open source. The code is public on GitHub under an open source licence. We show the licence on every page, including dual licences such as MIT OR Apache-2.0, because it decides what you may do with the code.
- It does something you can see. The format is a short video, so the repo has to do a visible job: an app, a tool, a skill for an AI agent, a simulation in the browser. Libraries that only make sense in code are hard to show honestly in under a minute, so they rarely make it.
- There is a way to try it. An install command, a release download or a hosted build. If the only path is to read the code, it waits.
- It is worth your time. We look for repos that replace a paid app, do one job unusually well, or are simply surprising. Star counts help us find them but do not decide for us: some picks have tens of thousands of stars and some have fewer than a hundred.
What the labels mean
Every post carries one label that says how much we did with the repo for the video. It is not a rating.
- We ran it. We installed the project and used it. What you see in the video is our own run.
- We built it from source. We compiled the code in the repo ourselves and ran that build.
- We ran the hosted build. The project hosts a live web version and we used that. We did not install it locally.
- Shown from the repo's own demo. We did not run it. The video uses the project's own published demo, screenshots and GitHub page. The post says so near the top, and the install steps are marked as coming from the README.
How we check facts
Star counts, licences, languages and creation dates come from the repository itself, and each page shows the date the stars were checked. Stars change every day, so treat the number as a snapshot. Install commands are copied from the project's README or docs exactly. Anything else a post claims links to a source at the bottom of the page.
The catch
Every repo post names one catch: the biggest limit we found or that the authors admit to. Young projects, missing features, a GPU requirement, unsigned installers, long run times. You should know it before you clone anything.
What we will not do
- Say we tested something we did not.
- Invent numbers, quotes, benchmarks or reviews.
- Take money to change a label or drop a catch.
- Post a repo built to find or track people who have not agreed to it.
Corrections
If a page is wrong or out of date, tell us. We fix the page and show an updated date next to the original one, so you can see it changed.
