Slop*Detector

INCONCLUSIVE — slop score 25/100

The evidence here points away from vibe coding rather than toward it. This is a standard Hypotheses/OpenEdition academic blog running a stock WordPress theme, and the hero image is a genuine candid photo of someone examining a Voynich Manuscript facsimile, not a render. The one structural flag worth noting is a dead Akismet privacy link, which is a common template leftover and not proof of AI authorship on its own. Writing-wise there's a single soft phrase, "making the timeline entirely manageable," that nudges toward filler, but one instance doesn't make a pattern. With a score of 25 and no clustering of tells, the fair read is a real academic post on an unmodified platform theme, inconclusive mostly because the broken link keeps it from a clean bill.

Findings

• Untouched shadcn/Tailwind defaults — shadcn components, lucide icons, and Inter/Geist/Space-Grotesk font stacks left at their defaults mean the model picked the design, not a person. Instrument Serif as an accent font is a separate, independently corroborated tell.
• Standard WordPress/Hypotheses theme, no custom design — This is a WordPress academic blog hosted on Hypotheses (OpenEdition), using a stock theme (bold condensed headline font, standard sidebar widgets, archive list, tag cloud). There's no evidence of templated AI-generated landing page patterns — this is a real human blog post from an academic.
• Real photography, not AI-generated imagery — The hero image is a genuine candid photograph of a person examining a physical facsimile of the Voynich Manuscript at a real desk, with natural lighting and plausible detail — no waxy rendering, no garbled text, no isometric sheen.
• Mild filler-conclusion phrasing — The clause 'making the timeline entirely manageable' reads as a slightly inflated, reassurance-style gloss tacked onto a straightforward scheduling fact, mildly echoing AI copy's tendency to editorialize obvious implications, though it's a single isolated instance.
• Dead Privacy Policy link — The Privacy Policy link exists but leads to an empty or broken page — the template put the link there and nobody wrote the page.