cal.diy vs next-forge

cal.diy and next-forge share 20 technologies: Next.js, Postgres, Redis, Sentry, Stripe, React, @next/third-parties, Vercel, PostHog, Zod, Tailwind CSS, next-themes, class-variance-authority, React Hook Form, sonner, Radix UI, Lucide, tailwind-merge, cmdk, and react-day-picker. Both are written in TypeScript.

Read it as markdown

What they share and what sets them apart

calcom

cal.diy

Scheduling infrastructure for absolutely everyone.

TypeScript50.2kRead on November 18, 2026, at commit ae027bbWhat is cal.diy built with?

Only in cal.diy

In common

Side by side

SizeLines written by people and agents, without generated ones; code files, without tests.
cal.diy554,770 lines written4,286 code files
next-forge26,893 lines written199 code files
Who writes itA commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
cal.diy6.3% of its commits signed by AIWith Devin, Claude Code, CodeRabbit, Cursor, and GitHub Copilot
next-forge0.6% of its commits signed by AIWith Claude Code and GitHub Copilot
ActivityFrom GitHub and its history, on the day SeeRepo read it.
cal.diyLast push November 13, 202616,072 commits50,151 stars
next-forgeLast push May 28, 20261,489 commits7,790 stars
TestsThe files that test the code, and the share of code files a test imports.
cal.diy645 test files14.9% of its code files have a test that imports them
next-forge3 test files1.5% of its code files have a test that imports them

Frequently asked questions

Which is bigger, cal.diy or next-forge?
cal.diy, with 554,770 lines written; next-forge has 26,893.

The proof: calcom/cal.diy's code at commit ae027bb

Which has more GitHub stars, cal.diy or next-forge?
cal.diy, with 50,151 stars; next-forge has 7,790.

The proof: calcom/cal.diy on GitHub

Which has more tests, cal.diy or next-forge?
cal.diy, with 645 test files; next-forge has 3.

The proof: calcom/cal.diy's code at commit ae027bb

Which was updated more recently, cal.diy or next-forge?
cal.diy: its last push was on November 13, 2026, and next-forge's on May 28, 2026.

The proof: calcom/cal.diy's commits on GitHub

Which has more commits signed by AI, cal.diy or next-forge?
cal.diy: an AI signed 6.3% of its commits, with Devin, Claude Code, CodeRabbit, Cursor, and GitHub Copilot; in next-forge, 0.6%.

The proof: the commits each tool signed in calcom/cal.diy

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.Private repo? Sign in with GitHub

Or look inside SeeRepo's own →