Anti-Slop — Opinionated Oxlint rules to catch low-quality TypeScript and JavaScript patterns.
Analyzed by Sai Pavan Gopularam · Developer Tools · Linting · View on GitHub
- Stars: 4129
- Forks: 89
- Commits last 30 days: 26
- Health: Active (26 commits this month)
- Language: TypeScript
- License: MIT
What It Is
Imagine a strict editor for your code that flags not just typos, but also awkward phrasing or unclear sentences. Anti-Slop is like that editor for your TypeScript and JavaScript, using Oxlint to enforce highly opinionated rules that go beyond standard linting to catch subtle, low-evidence coding patterns.
This matters because these subtle patterns often lead to hard-to-debug issues, unexpected runtime behavior, or simply make code harder to read and maintain. By enforcing these rules, Anti-Slop helps development teams write more robust, predictable, and higher-quality code, reducing technical debt and future headaches.
License Verdict
MIT License — Build and Sell Freely — Commercial Use Approved • No Copyleft Restrictions
The MIT License is highly permissive. You can use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software. You just need to include the original copyright and license notice in any substantial portions of the software. This makes it ideal for commercial products and services.
How to Use It
Anti-Slop is designed to be vendored directly into your project, not installed as a typical npm package. You can use a provided agent skill for initial setup, which copies the rules and configures Oxlint. Alternatively, manually copy the source files and update your `oxlint.config.ts`.
Prerequisites:
- Node.js
- Oxlint (compatible version)
Estimated setup time: 15 minutes.
npx skills add dmmulroy/anti-slop --skill install-anti-slop
# Manual setup (after copying src/):
npm install oxlint @oxlint/plugins --save-dev
# (Then configure oxlint.config.ts as per README)What I'd Build With This
Opinionated Code Review Bot (micro-saas)
Build a GitHub App that integrates with PRs. It automatically runs Anti-Slop rules against changed TypeScript/JavaScript files, commenting on violations with explanations and suggestions. This acts as an automated, strict code reviewer, saving teams time and enforcing consistency.
Effort: 2 Weeks Build Time · Target: Dev Teams, Open Source · Pricing: $19/mo per repo
Custom Linting as a Service (saas)
Develop a platform where dev teams can upload or connect their codebase. The service provides detailed code quality reports based on Anti-Slop and custom rules, offers a UI to manage active rules, tracks quality trends, and integrates with CI/CD pipelines as a quality gate. This provides a centralized solution for code quality enforcement.
Effort: 3 Months Build Time · Target: Mid-Market Tech Companies · Pricing: $199/mo - $999/mo (tier-based)
Code Quality Consulting & Custom Rule Dev (enterprise)
Offer specialized consulting services to large enterprises. This involves integrating Anti-Slop into their existing monorepos and CI/CD, adapting the rules to their specific architectural patterns, and developing new custom Oxlint rules based on internal best practices. The 'vendoring' nature of Anti-Slop makes it highly adaptable for bespoke enterprise needs.
Effort: Ongoing Service · Target: Large Enterprises · Pricing: Project-based, $10k - $50k+
Sai Pavan Gopularam's Take
This repo tackles a problem many developers face: subtle code quality issues that linters often miss. The 'vendoring' approach is unusual but makes sense for something so opinionated. I see a clear path to building a niche code quality consulting business around this, charging enterprises $10k+ per project to integrate and customize these rules for their specific needs.
Watch Out For
- Vendoring Required: Anti-Slop is designed to be copied directly into your repository (`vendored`), not installed via npm. This means you're responsible for maintaining and updating the rules yourself, rather than relying on package updates.
- Highly Opinionated: The ruleset reflects the author's specific preferences and taste. You'll need to review and potentially customize rules to align with your team's existing coding standards or preferences.
- Oxlint Dependency: This project requires Oxlint and its plugins. You'll need to ensure compatible versions are installed and maintained alongside Anti-Slop, especially during upgrades.
- Local Analysis Only: Rules use Oxlint's AST and lexical scope APIs, meaning they don't infer imported type definitions or cross-file call signatures. This limits some advanced type-based checks.
I break down trending repos like Anti-Slop every week — join the newsletter.