kitproof

Methodology

Every verdict on kitproof comes from public evidence you can check yourself. No hidden scores, and nothing is for sale.

Maintenance pulse

From commits on each kit's default branch, via the GitHub API.

ActiveCommits in the last 30 days
SteadyCommits in the last 90 days, none in the last 30
SlowingNo commits in 90 days; last one within 6 months
DormantNo commits in over 6 months
ArchivedArchived by its owner
Not verifiableNo public repository to check

Dependency freshness

We read the kit's package.json (including pnpm catalogs), take the lowest version each core dependency allows, and compare its major version to the npm "latest" release. Core dependencies include Next.js, React, Tailwind CSS, Prisma, Drizzle, Auth.js, Better Auth, Supabase, tRPC, Zod, the Vercel AI SDK, Astro, SvelteKit, and Expo. For 0.x packages, any minor-version gap counts as one breaking step.

Current depsCore dependencies on their latest major version
1 major behindAt least one core dependency is one breaking release behind
2+ majors behindA core dependency is two or more breaking releases behind
Deps unknownDependencies not publicly verifiable

TypeScript and the Stripe SDK are shown but not counted. Their major releases rarely change what a buyer gets: TypeScript 7 is a compiler rewrite, and Stripe SDK majors follow Stripe's API-version schedule.

Ranking

Within each category, kits are ordered by:

  1. Maintenance pulse (active → steady → slowing → not verifiable → dormant → archived)
  2. Dependency freshness (current → behind → unknown → stale)
  3. Commits in the last 90 days

Never used: GitHub stars (they're easy to fake), affiliate relationships, sponsorships, or paid placement. Sponsored placements, when we have them, are labeled and shown separately from the ranking.

For kit makers

Closed-source kits show "Not verifiable" because we can't see the code. That is not a judgment of quality. You can get verified by giving us read-only access to your repository or a public changelog, and you can correct factual errors at any time. You can't remove accurate evidence or buy a better verdict.

Data for tools and agents

Everything on the site is also available as JSON: /api/kits.json for all kits, or/api/kits/<id>.json for one. There's an RSS feed of changes and anllms.txt for AI assistants, plus an MCP server so coding agents (Claude Code, Cursor, and others) can check a kit before recommending it: tools check_starter_kit, find_starter_kits, and compare_starter_kits. Free to use with attribution and a link to each kit's evidence page.

Limits