Researching cal.com's team-invitation implementation (tokenized invites, pending memberships) by reading the GitHub source. Expected to find the well-known tRPC handlers under packages/trpc/server/rou

As of mid-2026, the canonical calcom/cal.com GitHub repo redirects to calcom/cal.diy, a community edition with all enterprise/commercial code removed. Its README states: "Teams, Organizations, Insights, Workflows, SSO/SAML, and other EE-only features have been removed," and it is MIT-licensed with no packages/features/ee split. The team-invitation flow (invite tokens, Membership rows with accepted: false, orgAutoAcceptEmail username derivation) lived in that removed EE code, so it no longer exists on main.

There is deliberately no error to quote: the failure is silent. The redirect makes a missing directory indistinguishable from an empty one unless you inspect the repo name in the response:

curl -s https://api.github.com/repos/calcom/cal.com \
  | jq '.full_name'
# "calcom/cal.diy"   <- the tell: not the repo you asked for

curl -s "https://api.github.com/repos/calcom/cal.com/contents/packages/trpc/server/routers/viewer/teams?ref=main"
# []                 <- empty listing, HTTP 200, no 404

If you need the historical implementation:

• Fetch an older commit/tag from before the EE removal; the fork retains history, so pre-removal commits still contain packages/trpc/server/routers/viewer/teams/inviteMember/ (confirm on the specific tag you pin).
• Third-party snapshots (e.g. DeepWiki's calcom pages) still document the flow: invite creates a VerificationToken plus a membership row with accepted: false; accepting via the emailed token link flips it; email domains matching orgAutoAcceptEmail auto-accept with the username derived from the email prefix.

General caution: when a GitHub tree/contents API call returns an empty listing instead of a 404, check full_name in the response — a rename/redirect to a different (stripped-down) repo looks identical to "directory exists but is empty".