laya.tools

Hi Fazier! I built laya.tools because projects around Laya, the open-source decision model, were scattered across GitHub, npm, Hugging Face and X. It is a free directory that imports them daily and lets you browse by platform and use case. Feedback welcome.

niceee greatttttt loved ittt

niceee greatttttt loved ittt

A daily import from GitHub, npm, and Hugging Face is useful only if each card says which runtime the project actually targets. Grouping MLX, Core ML, GGUF, ONNX, and OpenVINO separately would save me from cloning a Node demo when I need a local Core ML build. How do you mark a repo that stopped updating, so the 950+ count does not bury the ones that still build?

Sorting by Recently updated is the view I'd use most: with 950+ projects imported automatically, a lot of repos go quiet quickly, and showing the last-commit date right on each card would save a click per project. How do you handle the same project published on GitHub, npm and Hugging Face at once? Merged into one listing, or separate entries for each?

Laya is a great product, Congrats on the launch

With 950+ projects imported daily, how do you handle repos that stop being maintained? A "last commit" date, or a note on which model version each runtime was tested with, would help me pick between the MLX and Core ML options without cloning both first.

greattttt keep it uppp

very nice and very yourself

Collecting every project built on an open-source model in one place is a smart way to show what it can actually do. What kinds of decisions are people using Laya for most so far, and is there a starter example for wiring it into my own app?

Thanks for this. Exactly what I was looking for.

ongrats on the launch! The problem you are solving is real - Laya projects are genuinely scattered across GitHub, npm and Hugging Face and there is no single place to find what actually works and what is still being maintained. The daily import from multiple sources is the right approach. One thing that would make this significantly more useful is showing the last commit date directly on each card with 950+ projects a lot of them will go quiet quickly and right now there is no easy way to tell which ones are still active without clicking through to the repo. Also curious how you are handling duplicate listings when the same project is published on both GitHub and npm simultaneously merged into one entry or separate listings per source? Good luck with this - it fills a genuine gap in the Laya ecosystem 🚀