Is linear.app vibe coded?

Reading this score

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

What pushed it up

• Large language model house style +16 — 2 stock LLM marketing phrases.
• Copy that never says who it is for +9 — 1640 words, and still no price, no contact route and no named audience. The page describes a category, not a business.
• Fixed pixel widths that will overflow a phone +8 — Hard pixel widths wider than a phone. Layouts break at sizes nobody prompted for, because desktop was the only viewport that got looked at.
• The rule-of-three cadence +6 — 5 triplet lists and 0 “not just X — it's Y” constructions. Rhythm borrowed from marketing prose, with none of the content.
• Get Started / Learn More pairing +5 — The default CTA pair, untouched.

What pulled it down

• Deliberate social preview −9 — Open Graph title and image were both authored.
• Skip-to-content link −9 — A keyboard skip link exists. Generators do not do this.
• Hand-written ARIA −7 — 220 explicit accessibility attributes.
• Semantic landmarks −6 — 5 landmark elements instead of a pile of divs.
• CSS custom property system −6 — 804 CSS custom properties — a real token layer.
• 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.

• Structured data
• prefers-reduced-motion honoured
• Self-hosted typography
• Hand-authored stylesheet
• No utility-class soup

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.