oxlint
for frontend engineers
Why this scored 5
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Signal history
7-day window (free)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 119
ESLint took 4.4s to lint Vue's core. oxlint took 0.24s. Then I turned on the type-aware rules.
Oxlint dramatically speeds linting compared to ESLint, especially with type-aware rules. · for frontend engineers
devtoSteadydevtools28d ago - 215
anti-slop — Opinionated Oxlint rules for rejecting low-evidence TypeScript and JavaScript patterns
New linting rules available · for typescript devs
githubSteady 3 · javascriptdevtools−20 saturated60d ago