Skip to content

Open Source Project

A project site for a library: install command above the hero, the API in twenty lines, docs, changelog, roadmap, community, and who funds it said plainly.

7 routes7 pages · 21 blocks39 files · 4,604 lineslucide-reactAdded 14 Sept 2026

What's included

  • app/changelog/page.tsx
  • app/community/page.tsx
  • app/docs/page.tsx
  • app/globals.css
  • app/layout.tsx
  • app/not-found.tsx
  • and 11 more files
  • 7 pages it is built from, installed with it
  • Needs lucide-react

Works with

  • React
  • Next.js
  • Tailwind CSS
  • TypeScript

npx hoverlab init open-source ./my-app

Or over MCP, from your editor's agent — no account needed.

License

Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.

Was this useful?

Every screen

Install
npm install ratchet
MIT · v2.4.0 · 2.1M downloads a month

Schema migrations that refuse to break production

A migration runner that reads your application code before it drops a column, and blocks itself when something still needs it. Plain SQL, one static binary, no DSL.

ratchet up

The whole API is one object and two files

A config, and migrations that are plain SQL. If you already know how to write an ALTER TABLE you know how to use this.

  • Migrations are SQL files — nothing to learn, nothing to unlearn
  • The guard is the only unusual concept, and it is four lines
  • Irreversible migrations are declared, not inferred
import { Ratchet } from 'ratchet' // A migration is a file, not a class. The up is required; the down is// optional and, if you leave it out, the migration is declared// irreversible and the tool will say so rather than guess.export const ratchet = new Ratchet({  dir: './migrations',  url: process.env.DATABASE_URL,   // The whole point of the library. Before applying anything that drops  // or narrows a column, parse the queries in these paths and refuse if  // one of them still reads it.  guard: {    scan: ['api/**/*.go', 'reports/**/*.sql'],    onConflict: 'block',  },}) await ratchet.up()

Why this rather than the one you already have

Five differences. The first one is the reason the project exists; the others are consequences of keeping it small.

It reads your code before it drops a column

The guard parses the queries in the paths you name and blocks a destructive migration while anything still reads the column. Most outages caused by a migration are this exact shape.

Plain SQL, no DSL

Your database’s own documentation is the reference. Nothing to learn and nothing that stops working when Postgres adds a feature.

Irreversible is a thing you declare

A migration with no down is fine — lying about it is not. Say so in a comment and the plan output says so too.

No lock held while it thinks

Planning happens before the transaction opens, so a slow guard scan never holds a lock on a production table.

One binary, no runtime

6MB, static, no Node or Python needed in the image that runs it. The library and the CLI are the same code.

18.4k
GitHub stars
And 312 open issues, honestly
2.1M
Downloads a month
npm, last 30 days
184
Contributors
41 with commit access
MIT
Licence
Since 2021, and it will not change

Funding, since you are about to depend on it

Two maintainers are paid part-time; the rest is volunteered

Northwind funds one day a week and Contoso funds two, both on rolling twelve-month agreements, and neither gets any say over the roadmap — that is written into both. If both stopped tomorrow the project would keep going more slowly rather than stopping, because no single contributor holds more than 19% of commits. This paragraph is here because it is the question a team should ask before taking a dependency, and most projects do not answer it.

£61k
Funded in 2025
Two corporate sponsors, 340 individuals
3 days
Paid maintainer time a week
Across two people
19%
Largest share of commits
No single point of failure
0
Sponsor influence on the roadmap
Written into both agreements

Live components in your current theme — switch routes, or the phone icon to check the mobile layout. Colours are this template’s Carbon palette, which ships in app/globals.css. A near-neutral grey with a violet cast and a near-black primary. The palette an open-source project converges on because it stays out of the way of a code sample, which is the only thing on the page anybody came for.

Get it

39 files · .zip · nothing to configure

then

cd open-source
npm install
npm run dev

The archive contains the whole project — routes, blocks, theme tokens, Tailwind and PostCSS config, tsconfig and a .gitignore. One runtime dependency, and no Hoverlab dependency at all: it is your code from the moment it unzips.

For AI

The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.

See the prompt

Routes

PathPageFile
/Open Source Projectapp/page.tsx
/docsDocumentation Pageapp/docs/page.tsx
/changelogChangelog Pageapp/changelog/page.tsx
/roadmapPublic Roadmapapp/roadmap/page.tsx
/communityCommunity Pageapp/community/page.tsx
/sponsorPricing Pageapp/sponsor/page.tsx
404404 Pageapp/not-found.tsx

What you get

project root(8 files)

  • GETTING-STARTED.md
  • gitignore
  • next.config.ts
  • package.json
  • postcss.config.mjs
  • README.md
  • tailwind.config.ts
  • tsconfig.json

app/(9 files)

  • changelog/page.tsx
  • community/page.tsx
  • docs/page.tsx
  • globals.css
  • layout.tsx
  • not-found.tsx
  • page.tsx
  • roadmap/page.tsx
  • sponsor/page.tsx

components/(22 files)

  • bento-features.tsx
  • changelog-timeline.tsx
  • code-showcase.tsx
  • code-tabs-panel.tsx
  • community-band.tsx
  • comparison-table.tsx
  • docs-layout.tsx
  • faq-accordion.tsx
  • feedback-widget.tsx
  • footer-mega.tsx
  • footer-minimal.tsx
  • hero-terminal.tsx
  • logo-segments.tsx
  • navbar-simple.tsx
  • newsletter-signup.tsx
  • not-found-404.tsx
  • pricing-tiers.tsx
  • roadmap-columns.tsx
  • stats-band.tsx
  • stats-narrative.tsx
  • testimonial-grid.tsx
  • theme-provider.tsx

Every file is listed. The 21 files in components/ are the blocks the pages import — each one has its own page if you want to read it on its own.

Project files

Everything except the blocks. Opens on app/globals.css — the file that makes the rest look right, since every block styles itself with bg-card and text-muted-foreground rather than literal colours.

app/globals.css
@tailwind base;
@tailwind components;
@tailwind utilities;

/**
 * Design tokens — the Carbon palette.
 *
 * A near-neutral grey with a violet cast and a near-black primary. The palette an open-source project converges on because it stays out of the way of a code sample, which is the only thing on the page anybody came for.
 *
 * This file is the reason a pasted block looks right. Every block and page
 * styles itself with semantic classes — `bg-card`, `text-muted-foreground`,
 * `border-border` — rather than literal colours, so they inherit whatever
 * you define here instead of fighting it. Change a value below and every
 * section in the project moves with it. Change the hue on `--primary` and
 * `--ring` together and you have rebranded the site.
 *
 * Values are bare HSL channels, not `hsl(...)` calls. That is what lets
 * Tailwind compose them with an alpha suffix: `bg-primary/10` expands to
 * `hsl(var(--primary) / 0.1)`, which is impossible if the variable already
 * carries its own function wrapper.
 *
 * Every foreground/background pair below clears WCAG AA (4.5:1) in both
 * themes. If you retune one, check the pair rather than trusting the eye —
 * mid-lightness accents are the ones that fail.
 */

@layer base {
  :root {
    --background: 260 12% 99%;
    --foreground: 260 12% 9%;
    --card: 0 0% 100%;
    --card-foreground: 260 12% 9%;
    --popover: 0 0% 100%;
    --popover-foreground: 260 12% 9%;
    --primary: 260 12% 16%;
    --primary-foreground: 0 0% 100%;
    --secondary: 260 14% 96%;
    --secondary-foreground: 260 12% 20%;
    --muted: 260 12% 96%;
    --muted-foreground: 260 12% 42%;
    --accent: 276 12% 95%;
    --accent-foreground: 276 12% 22%;
    --destructive: 0 72% 45%;
    --destructive-foreground: 0 0% 100%;
    --border: 260 12% 90%;
    --input: 260 12% 90%;
    --ring: 260 12% 16%;

    --radius: 0.25rem;
  }

  .dark {
    --background: 260 12% 5%;
    --foreground: 260 15% 97%;
    --card: 260 12% 8%;
    --card-foreground: 260 15% 97%;
    --popover: 260 12% 8%;
    --popover-foreground: 260 15% 97%;
    --primary: 260 12% 78%;
    --primary-foreground: 260 12% 8%;
    --secondary: 260 12% 15%;
    --secondary-foreground: 260 15% 97%;
    --muted: 260 12% 15%;
    --muted-foreground: 260 12% 68%;
    --accent: 276 12% 18%;
    --accent-foreground: 276 12% 92%;
    --destructive: 0 62% 52%;
    --destructive-foreground: 0 0% 100%;
    --border: 260 12% 19%;
    --input: 260 12% 19%;
    --ring: 260 12% 78%;
  }
}

@layer base {
  * {
    @apply border-border;
  }

  body {
    @apply bg-background text-foreground antialiased;
  }

  /**
   * Global motion opt-out.
   *
   * Blocks guard their own animations with Tailwind's `motion-safe:`, but
   * third-party CSS and anything you add later will not. This is the
   * backstop: it neutralises every animation and transition on the page
   * for users who have asked the OS for reduced motion, rather than
   * relying on each author to remember.
   */
  @media (prefers-reduced-motion: reduce) {
    *,
    *::before,
    *::after {
      animation-duration: 0.01ms !important;
      animation-iteration-count: 1 !important;
      transition-duration: 0.01ms !important;
      scroll-behavior: auto !important;
    }
  }
}

More Marketing

Open the full page for this template

Marketing Site

A pricing page that answers the objection

Landing page, pricing page, 404. The smallest thing you can put in front of a product and have it look deliberate.

3 routes3 pages13 blocksVermilion
Pro
Open the full page for this template

Content Site

The article at a real measure

A publication that happens to belong to a company: blog index, article, careers and a 404. The site for when the writing is the product — or the marketing.

4 routes4 pages10 blocksInk
Pro
Open the full page for this template

Docs Site

The three-column docs frame

The three-column docs frame — sidebar, article, on-this-page rail — plus a changelog and a 404. The part of the product a search for an error message should find.

3 routes3 pages6 blocksAzure
Pro
Open the full page for this template

Help Centre

Search that answers before the ticket

The support surface, as four routes that agree with each other: searchable answers, the docs, what changed, and a status page carrying the same incident the help page announces.

5 routes5 pages13 blocksRose
Pro
Open the full page for this template

Developer Portfolio

The terminal that introduces you

An engineer’s site rather than a designer’s: a terminal hero, thirty legible lines of real code on the home page, the projects, the writing and a CV that prints.

8 routes8 pages26 blocksPhosphor
Open the full page for this template

Personal Résumé

A CV that prints properly

A minimal personal site whose home page is the CV itself — printable, indexable, and therefore the copy that actually gets maintained. Five routes, warm paper, square corners.

6 routes6 pages17 blocksLinen
Pro
Open the full page for this template

Crypto Exchange

The live price rail

A regulated exchange, front to back: a moving price rail, a public markets screen, the custody facts, the fee schedule and the risk warning as a section rather than as small print.

8 routes8 pages30 blocksVault
Pro
Open the full page for this template

Conference Site

The agenda across three tracks

An event site built around a date: the ticket price step-up above the hero, a two-day programme across three tracks, speakers, venue and a code of conduct.

7 routes7 pages25 blocksMarquee
Pro
Open the full page for this template

Restaurant

The menu, typeset as a bill of fare

A dining room’s whole site: hours and phone above the fold, the menu typeset as a bill of fare, a real reservation flow, the room and the way to find it.

7 routes7 pages24 blocksLaurel
Pro
Open the full page for this template

Estate Agency

Map and results, scrolling apart

Property search with results already in it, a listing page that puts tenure and EPC above the prose, the agents, and a valuation route for the other half of the business.

6 routes6 pages23 blocksHeath
Pro
Open the full page for this template

Job Board

Salary on every row, grouped by craft

A two-sided board where candidates get the whole site and employers get one section and a price. Listings grouped by craft, each with a real salary range and the interview process published.

6 routes6 pages28 blocksFoundry
Pro
Open the full page for this template

Directory

Facets that are not categories

A faceted index with a listing page that compares each entry against its alternatives, a paid submission route, and a published removal rate.

6 routes6 pages29 blocksMulberry
Pro
Open the full page for this template

Streaming Service

The watch screen, on the marketing page

A subscription video service: catalogue rails, a real watch screen with chapters and a transcript, one plan at one price, and the account behind it.

6 routes6 pages20 blocksNocturne