Slop*Detector

INCONCLUSIVE — slop score 38/100

The README itself reads clean: specific CLI details, a blockquote about the rename from cargo-pretty-build, and lines like "Feed it a verb it doesn't know and it takes it personally" suggest a person actually wrote the docs. The trouble sits in the legal pages. The Terms of Service and Privacy Policy both carry the classic reframe pattern and stray em dashes, plus the word "utilize," which suggests those pages got dropped in from a generator and never touched by a human editor. The glassmorphism panels and pill badges flagged in the scan turn out to be ordinary GitHub chrome, so they don't add much weight either way. Given the split between authentic project writing and boilerplate legal text, the case lands as inconclusive at 38 out of 100: the code and docs feel handmade, but whoever shipped this outsourced the policy pages without a second look.

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.
• Standard GitHub repo README page — This is a stock GitHub repository page, not a custom marketing site — there's no custom visual design to evaluate for AI-generated hero/gradient/pill tells since GitHub's own UI is the only 'design' present.
• No pill tags (minor) — The README contains small rounded badge-like elements (status badge, license badge, inline code chips), but these are ordinary GitHub badge conventions (shields.io-style build/license badges) and inline code formatting, not AI-generated marketing pill tags.
• Coherent, specific, non-templated copy — The README text is highly specific, technical, and idiosyncratic (discusses real CLI flags, actual renaming history, concrete behavior like 'six crates in flight at once'), which reads as genuinely human-authored documentation rather than generic templated feature copy.
• AI vocabulary — Words statistically overrepresented in generated text: "seamless", "leverage", "unlock", "empower", "elevate", "robust" and friends.
• 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.