Is basecamp.com vibe coded?

Reading this score

basecamp.com landed on 7/100, which puts it in the hand-written band. That number is not a percentage and not a probability — it is strength of evidence: 14 points of tells, damped by craft, less 39 points of deliberate decisions, mapped through one logistic curve.

What pushed it up

• The standard landing page skeleton +12 — 5 of the seven stock sections are present. Hero, logo bar, three features, stats, testimonials, pricing, FAQ, CTA, footer — every section present, none earning its place.
• Only the happy path was built +7 — A client-rendered page with no loading, empty or error affordance anywhere in the markup — not even a <noscript>. Slow network, zero results, failed request: blank screen.
• The rule-of-three cadence +6 — 7 triplet lists and 0 “not just X — it's Y” constructions. Rhythm borrowed from marketing prose, with none of the content.

What pulled it down

• Deliberate social preview −9 — Open Graph title and image were both authored.
• Hand-written ARIA −7 — 58 explicit accessibility attributes.
• No utility-class soup −7 — Not one Tailwind utility class in the markup.
• Structured data −6 — JSON-LD is present — somebody thought about search.
• Semantic landmarks −6 — 5 landmark elements instead of a pile of divs.
• Canonical URL −4 — Canonical link is set.

Craft we looked for and did not find

These are the actionable half of the report. None of them are hard, and every one of them would have moved the number.

• Skip-to-content link
• prefers-reduced-motion honoured
• Self-hosted typography
• CSS custom property system
• Hand-authored stylesheet

What this scan cannot see

One request, no JavaScript executed. So everything below is invisible to us, and a page can be excellent or awful at all of it without moving the score:

• Domain registration age — needs WHOIS.
• Whether the nav's /about and /pricing actually resolve — needs a crawl, not one fetch.
• package.json dependency count, orphaned code, clashing abstractions, test coverage — needs the repo.
• Backend security shortcuts: string-built SQL, verify=False, missing auth on endpoints — needs the source.
• Whether row-level security or Firebase rules are actually switched on — needs the project.
• Console errors, hydration warnings and runtime 404s — needs a browser executing the page.
• Real Lighthouse numbers and horizontal scroll at 375px — needs a rendered viewport.
• Whether a JS-handled form posts anywhere — needs a submitted request.