AISlop ships CLI and GitHub Action to catch AI-generated code smells

Why it matters

AI-written code is entering codebases fast. A CI gate tuned for AI-specific smells gives teams a simple way to catch weak patterns early and keep PR quality up.

AISlop, a command-line tool and GitHub Action that flags AI-generated code smells, is now live on GitHub and the GitHub Marketplace, per the repository and the AISlop Quality Gate listing.

What shipped

Hosted under the GitHub account scanaislop, AISlop positions itself as a quality gate developers can add to CI to scan for patterns associated with AI-written code. The repo surfaces a one-click Marketplace path to "Add this Action to an existing workflow or create a new one," and shows an actively maintained codebase with 2 branches, 25 tags, and 107 commits.

A recent release tagged in the codebase highlights a "v0.5.0" milestone that calls out a "CLI UX rehaul" and "in-house engines" (per the release commit reference). The Action is presented as a "Quality Gate" for CI workflows, while the commit history and directory structure indicate a CLI is also available for local use.

Under the hood and naming

Earlier work renamed the project from "slop" to "aislop" for publishing due to an npm package conflict, while keeping internal identifiers stable. As the maintainers wrote in a commit message: "The npm package name 'slop' is taken, so rename the entire project to 'aislop' for publishing... the ai-slop engine name, ai-slop/* rule identifiers, and 'AI Slop' category labels are intentionally preserved" (see the rename commit). That phrasing, along with the rule identifiers, suggests a ruleset explicitly focused on detecting telltale AI patterns.

Project cadence and community signals

Development appears active. The latest commit on main merged PR #136 from the develop branch on May 27, 2026 (authored by heavykenny; see the merge commit). Repository metadata on the page shows 49 stars and 5 forks.

The maintainers also enabled a community feedback loop aimed at improving rule accuracy and coverage. A documentation update added GitHub Discussions templates for false-positive reports and new rule requests, and linked those surfaces from the README so visitors can find them (per this community commit).

What we do and do not know

• Supported languages and frameworks are not listed in the provided snippets. The presence of in-house engines and the ai-slop/* rule taxonomy indicates a custom rules engine, but precise coverage is not stated here.
• The Marketplace presence confirms GitHub Actions support. The CLI exists (via commits referencing CLI UX), but installation steps and npm package coordinates are not shown in the excerpts.
• No individual maintainer names or a corporate entity are identified beyond GitHub handles and the repo owner.

For engineering leaders experimenting with AI in the stack, AISlop offers a pragmatic stance: bring a rules-based gate into CI to automatically flag questionable patterns before they land on main. For teams worried about creeping sloppiness from AI-assisted contributions, a guard like this can become a lightweight governance layer alongside linters and tests.