Is this still an active project

[dkokotov]

It feels like momentum on the project has stalled - no commits in last ~3 months, v1 still on a branch, no engagement with recently filed issues or open PRs.

It would be useful if @mattpocock could provide an update of whether there is any plan to continue pushing this forward and resuming to develop it actively. I was initially excited by this as it seemed to hit a sweet spot of a lightweight, easy to use eval tests framework, and started using it in my codebase. but it's hard to invest more in building a suite atop it with such an uncertain future.

This is not a complaint - I totally understand that priorities change. Matt is producing awesome content for the community and perhaps feels his time is better spent on other things. If that's the case it would just be good to make this explicit.

[p32929]

@dkokotov the question you're actually asking — "how much more can I safely build on this" — has an answer that doesn't need @mattpocock to reply.

Evalite's runtime surface is small and the risk isn't evenly spread, so you can de-risk without migrating off:

• Keep your evals framework-agnostic at the edges. The evalite(...) / Eval(...) wrapper is trivial to reimplement; the things that would hurt to lose are the scorer contract and the reporter/UI. Write scorers as plain async functions with no evalite import and register them at the call site — then a migration is a codemod on the wrapper, not a rewrite of the suite.
• Pin exactly and vendor the UI if you rely on it. An unmaintained package's real failure mode isn't the package, it's a transitive dep going incompatible (the vitest peer here is the one to watch — evalite rides Vitest's runner, and Vitest majors move faster than this repo has been moving).
• v1-on-a-branch is the signal to weigh most. An unreleased major that the author stopped merging into is the pattern that most reliably predicts no further releases — more than commit gaps do, since those often just mean a busy quarter.

None of that requires a decision from you today, and all of it is worth doing even if he does come back to it.

---

Not affiliated with this repo — I'm a Flutter/React/Node contractor and this is the kind of thing I get hired for. If you'd rather not own the fork yourself, I do it as fixed-price work through Fiverr escrow (you only release on a build that passes): https://www.fiverr.com/fayazbinsalam · https://github.com/p32929. Ignore this line if not useful — the fix above stands on its own.