Slop*Detector

CERTIFIED SLOP — slop score 77/100

The repository page itself is stock GitHub chrome, but the README and legal pages carry the tells that push this file into slop territory. Em dashes turn up everywhere, from the changelog entries to the Terms of Service and Privacy Policy, and those same legal pages stack the classic reframe language on top of it. Add in the emoji-prefixed headings like "🌟 Key Features" and "📚 Function Categories," the pill tags, and six elements running backdrop blur, and you get a page dressed in the same generated-UI garnish regardless of how technical the underlying content is. The README's dense algorithm lists (Risch-Norman, Gosper, Pollard's Rho) show real substance and keep the score from going higher, but the surrounding copy and boilerplate legal text weren't reviewed by a person before shipping. At 77, this reads as a genuine project wrapped in unedited AI-generated packaging rather than a fully synthetic site.

Findings

• Pill tags — Little fully-rounded pill badges sprinkled across the page ("New", "Beta", category chips) are a default garnish of vibe-coded UI.
• Emoji-prefixed headings — Feature headings that open with 🚀 or ✨ are generated-copy garnish.
• Glassmorphism — Frosted-glass backdrop-blur panels are a recurring generated-UI decoration.
• No stock UI cliches present — This is a raw GitHub repository page, not a marketed landing page — there's no hero, no gradient wash, no pill badges, no feature-tile grid, no CTA pair, and no illustration. GitHub's own chrome (top nav, About sidebar, README renderer) accounts for essentially all visual styling here.
• README content is dense, technical prose rather than templated marketing copy — The README describes extremely specific technical claims (line counts, module counts, named algorithms like Risch-Norman, Cherry/Liouvillian, Gruntz, Pollard's Rho, ECM) organized into genuine functional categories rather than generic aspirational blurbs — the opposite of filler feature-tile text.
• Em dashes — Em dashes are the single most reliable punctuation tell of LLM copy. Human marketing copy almost never uses them; models reach for them constantly.
• Compulsive rule-of-three — "Fast, reliable, and secure." Triads everywhere read as machine rhythm — humans vary list length; models default to three.
• Stiff, uncontracted prose — Expanded forms ("it is", "you will", "do not") dominating over contractions reads as robotic formality — either legal text or a language model.
• Sparkle/rocket emoji — ✨ and 🚀 scattered through headings and feature lists are the default garnish of generated landing copy.
• Em dash usage — Several em dashes appear throughout the README (e.g., in feature lists and asides), which the style guide flags as an AI tell, though here they're used in fairly standard technical-writing fashion (parenthetical asides, appositives) rather than dramatic rhetorical pauses.
• 'From X to Y' sweep phrasing — One instance of the sweeping-range construction appears, though it's followed immediately by a long, highly specific list of real subsystems rather than vague generalities, which undercuts the usual 'says nothing specific' complaint.
• 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.