Blog / Questions / FIG. 69
What Is awesome-jev? The Ecosystem's Front Door on GitHub
awesome-jev is the community-curated GitHub list of Jev tools, SDKs, and resources. What lives there, how it differs from this directory, why both exist.
Every technology that survives its launch week gets an "awesome" list, the GitHub-native genre of curated links, and Jev's arrived on schedule: awesome-jev is the community-maintained index of the ecosystem's tooling. If this site is the museum of what people built, awesome-jev is the hardware store of what people build with.
What lives there, per its current shape: the client libraries (jev-harness for TypeScript, jevclient for async Python, swift-typesafe, the req_llm Elixir provider), utility tooling like jev-tree for choice-cap recursion and fast-jev-compaction for coding agents, interface experiments like the Ask Jev extension, open-pattern projects like TypeLLM, and pointers to directories including this one. It's also, quietly, the best single indicator of ecosystem health: watch what gets added weekly and you're watching where builder energy actually flows, which the launch-week story could only snapshot.
How to use it well: as a discovery surface, not an endorsement engine. Awesome lists index existence, not quality, so the standing open-source diligence applies to everything linked, pin versions, read maintenance signals, and keep production habits independent of any dependency's promises. And how the two directories divide labor, since people ask: awesome-jev catalogs tools by category; this site catalogs builds with receipts, author-reported numbers linked per entry. Different questions, deliberately: "what can I use?" versus "what has it actually done, and what did that cost?" The ecosystem needs both answered, which is why we link them and they link us.
Frequently asked questions
Who maintains awesome-jev?
Community members, in the standard GitHub model: pull requests in, maintainer review, no official TypeSafe involvement implied by inclusion.
How do I get a project listed there?
The usual awesome-list route: a PR following its contribution format. Working builds with numbers also belong submitted here; the receipts requirement is ours, not theirs.
Is everything on the list safe to use?
Listing means discovered, not audited: apply normal dependency diligence, and keep your security posture independent of what any index implies.
Numbers throughout are as reported by the build authors, not verified by shipwithjev. Code-shaped examples are pseudocode; the official docs live at docs.typesafe.ai.