The first question is whether it knows your stack.
26 languages and 146 framework spec files, with real syntax trees for most of them and line-level analysis where a grammar is not wired in yet. Pick your language below and you get the honest answer for it: how it is parsed, what it catches, and where the coverage thins out.
Find your language and read what happens to it.
Every entry says how the file is parsed, which framework specs apply, and four things it looks for by name.
TypeScript
Full parseThe deepest coverage in the engine: 83 core patterns plus React/Next.js and testing specs.
4,808 patterns, and this is how they are distributed.
A total is easy to publish and hard to check, so here is the breakdown behind it, straight from the library. If your work sits mostly in one of these rows, that row is the number that matters to you, not the headline.
read from the pattern library at build time · a domain is a group of spec files, not a product tier