Slop*Detector

INCONCLUSIVE — slop score 46/100

The evidence here is a mixed bag, and the 46/100 score reflects that split rather than any single smoking gun. Most of the visual tells (the backdrop-blur panels, the rounded pill badges on repo stats) come from GitHub's own interface chrome, so they say nothing about the project itself. What actually moves the needle is the README: it has a 'Who Are You?' section that explicitly addresses an 'AI Coding Assistant' persona and includes a bolded CRITICAL directive telling LLMs they must read a coding-assistants doc before contributing, which is a structural choice no human-only audience would need. That's backed up by a commit log entry titled 'README: remove out of place emdashes,' meaning AI-flavored prose got into the file at some point and someone had to go clean it out by hand. Add in a Terms of Service and Privacy Policy riddled with em dashes and reframe constructions, and you get a project where the core code history is clearly organic but the surrounding documentation and platform text show real AI fingerprints, which is exactly why this one lands as inconclusive instead of a clean pass or a clear flag.

Findings

• Pill tags — Little fully-rounded pill badges sprinkled across the page ("New", "Beta", category chips) are a default garnish of vibe-coded UI.
• Glassmorphism — Frosted-glass backdrop-blur panels are a recurring generated-UI decoration.
• README edited for AI audience — The README contains a 'Who Are You?' section listing personas including 'AI Coding Assistant: LLMs and AI-powered development tools' and a bolded 'CRITICAL' directive addressed specifically to LLMs instructing them to read a coding-assistants doc before contributing — this is an unusual structural addition clearly written to be consumed by AI tools rather than organic kernel documentation style.
• Redundant persona-based section structure — The README breaks into many near-identical persona subsections (New Kernel Developer, Academic Researcher, Security Expert, Backport/Maintenance Engineer, System Administrator, Maintainer, Hardware Vendor, Distribution Maintainer, AI Coding Assistant), each following the same kicker + one-line blurb + bullet-list-of-links template — a mechanically repeated hierarchy rather than organic documentation prose.
• Commit message referencing AI-tell cleanup — A commit titled 'README: remove out of place emdashes' suggests the README previously contained AI-writing-style em dashes that had to be manually stripped out, which is corroborating evidence that AI-generated content was introduced into this file at some point and later cleaned up.
• Hollow superlatives — "Revolutionary", "world-class", "lightning-fast", "AI-powered" — claims with no content behind them.
• Role-based audience segmentation list — The 'Who Are You?' section lists reader roles (Developer, Researcher, Security Expert, etc.) similar to audience-segmentation patterns sometimes seen in generated marketing docs, but here it is used functionally to route to real documentation files rather than as rhetorical filler, so it reads as a legitimate navigation aid rather than an AI tell.
• Terms of Service reads as generated — The Terms of Service carries multiple AI-writing tells (em dashes, "it’s not x. it’s y." reframe). Generated legal pages are a strong marker of an unreviewed, vibe-coded ship.
• Privacy Policy reads as generated — The Privacy Policy carries multiple AI-writing tells (em dashes, ai vocabulary). Generated legal pages are a strong marker of an unreviewed, vibe-coded ship.