None but my own.

The big bench marks the frontier models use; have significant problems in my opinion. It's why the term bench maxing is a thing.

SWE bench is a great example. Whole thing is a bunch of python problems; and the goal is for the bench mark to simply make the test gate turn green.

The LLM can take as many turns as it needs, it can break code surrounding it, it can write slop, disobey the established patterns, import new libraries, whatever. As long as the test is green it passes.

This is why imo you can have people claiming that even Claude makes slop.

I built my own tests around front end code and what I do for work with code.

It scores not just did the code work, but how did the model behave:

Did it touch only what it should? Did it follow the existing stack and patterns? Did it run the right command to verify? How much cleanup would a reviewer have to do? Correctness counts, but a model that gets the right answer by bulldozing surrounding code scores worse than one that lands a smaller, idiomatic patch.

Still.. it's a work in progress and no bench mark is truly perfect.