WasItVibed Analyzes Public Websites Across 46 Deterministic Rules for AI-Generated Code
WasItVibed launched a scanner using 46 rule-based heuristics rather than statistical classifiers to detect AI-generated frontend code. It identifies platform deploy signatures from builders like v0, Bolt, Lovable, and Base44.
Impact: Medium
Why it matters
Audit your vibe-coded production builds to eliminate boilerplate artifacts, telltale class patterns, and third-party builder CDN dependencies before shipping.
TL;DR
- 01Identifies 46 deterministic markers across markup, styles, and hosting infrastructure.
- 02Flags distinct platform artifacts left by v0, Bolt, Lovable, and Base44.
- 03Publishes public report cards with individual rule breakdowns for audited URLs.
Key facts
- Evaluation Rules
- 46 published deterministic checks
- Detection Method
- Rule-based pattern matching (no AI model)
Deterministic Rules Instead of AI Classifiers
WasItVibed inspects client-facing assets using 46 explicit heuristics. Instead of feeding site copy back into an LLM classifier, it checks DOM layout, framework metadata, and compiled stylesheets directly.
Platform Signatures and CDN Footprints
The scanner detects platform-specific footprints left behind during rapid visual builds:
- v0 and Bolt: Deployment subdomains and hosted development domains.
- Lovable and Base44: Embedded builder CDN paths and script inclusions.
- Design Patterns: Heavy div nesting ("div soup"), uncurated glassmorphism, default Tailwind utility stacks, and generic multi-section landing sequences.
Handling Client-Rendered Shells
When a site relies heavily on client-side hydration leaving an empty initial HTML payload, the scanner evaluates compiled CSS and framework bootstrap code, automatically down-weighting confidence scores where structural evidence cannot be extracted.
✓ When to use
- Pre-release hygiene checks on frontend code built with AI coding assistants.
- Reviewing freelance or outsourced web submissions for raw generated boilerplate.
✕ When NOT to use
- Private internal microfrontends hosted behind authentication or corporate VPNs.
- Websites where you do not want public inspection results published to an indexed leaderboard.
What to do today
- Run your staging URL through the scanner to audit builder-injected CDN scripts.
- Refactor repetitive Tailwind class chains into clean component abstractions before production export.
- Migrate off vendor preview domains (v0, Bolt) to custom hosting infrastructure.
Sources