Five checks before adding a project
Confirm existence, integration, licensing, limitations and evidence-backed claims.
Start with evidence, not popularity
Check the original repository or author page, an explicit Jev connection, integration files, license and runtime instructions. Mentioning “AI” or “TypeSafe” alone does not establish a Jev integration.
This snapshot reviews public sources and resource positioning; it does not claim to have executed every project. Comparisons, screenshots and author reports should retain their provenance.
Leave unverified information unknown
This edition omits unverified stars, prices, latest versions and success rates. Future automation should record each value with its timestamp and source, preserving unknown values rather than inventing numbers.
Track license, maintenance, runtime compatibility and actual cost separately. A public repository does not imply free use for every purpose.
Consider the model's limitations
The official Jev 1.13 limitation notes and workflow evaluations serve different purposes: one documents failures, while the other must be interpreted within its published test conditions.Known limitations · Official evaluations
For directory maintenance, see Awesome Jev Projects source-verification materials; do not automatically adopt a third-party directory's certification criteria.