Developer dmmulroy released anti-slop, a set of opinionated Oxlint rules that reject low-evidence TypeScript and JavaScript patterns, according to the project's GitHub repository. The project's README defines low-evidence code as patterns that look type-safe but are not actually enforced by the compiler.
The rule set includes 15 generic rules targeting patterns such as chained type assertions, conditional empty object spreads, module mocking and unsafe dictionary types, plus a separate rule targeting architecture violations in codebases built on the Effect library.
Rather than shipping as a fixed npm dependency, anti-slop is designed to be vendored: copied directly into a repository and customized, or installed through an agent skill with the command "npx skills add dmmulroy/anti-slop," according to the repository. It is released under the MIT license and had drawn more than 3,400 GitHub stars.
The rules read like a reaction to how AI coding agents write TypeScript under time pressure: reach for an unsafe cast or a broad type to make an error go away instead of fixing the actual mismatch. A vendored lint rule set is a lightweight way to catch that pattern in review before it ships, without waiting on Oxlint itself to add the rule upstream.