meetai - Moses Yebei

meetai

Abstract

Meet.AI is a powerful, full-stack AI platform designed to help users create, manage, and interact with custom AI agents in seconds. From secure authentication to AI-powered meeting assistants, Meet.AI blends advanced technologies into an intuitive, production-ready app.

The Problem

Enterprises that want on‑demand AI assistants must stitch together authentication, database, AI APIs, and real‑time video/chat. Doing this from scratch costs weeks of engineering and introduces security gaps.

What This Does

meetai delivers a production‑ready stack that lets a user create an AI “agent”, schedule a meeting, and run a live AI‑powered assistant during the call. Core features live in the src folder:

Authentication – src/app/(auth)/* and src/lib/auth.ts use BetterAuth for magic‑link, social logins, and TOTP 2FA.
Agent & Meeting Management – UI components under src/modules/agents/ui and src/modules/meetings/ui interact with Drizzle ORM schemas (src/db/schema.ts) via TRPC procedures (src/modules/*/server/procedures.ts).
AI Services – src/lib/email/templates/*.ts and src/lib/stream‑chat.tsx call OpenAI (GPT‑4o) and Stream.io.
Background Jobs – Inngest functions (src/inngest/functions.ts) handle email delivery and post‑meeting summarisation.

The app is built with Next.js 15 (App Router), TypeScript, Tailwind CSS, and React Hook Form + Zod for validation.

How It Is Wired

Execution starts at the Next.js server entry defined in next.config.ts. A request to /api/trpc/[trpc] is handled by src/app/api/trpc/[trpc]/route.ts, which creates a TRPC router (src/trpc/*) that forwards calls to module‑level procedures, e.g.:

src/modules/agents/server/procedures.ts → src/db/index.ts (Drizzle) → PostgreSQL.
src/modules/meetings/server/procedures.ts → src/lib/email/index.ts (nodemailer) → SMTP.

The most connected module is src/modules/meetings/types (imported by 8 other files, no outgoing imports), making it a low‑risk data definition hub. Conversely, src/modules/meetings/ui/views/meeting-id-view imports 7 UI components, giving it an instability of 1 (high blast radius). The largest single file, src/components/ui/sidebar.tsx (661 LOC), aggregates navigation logic used across dashboard pages, so any change ripples through many routes.

Deep nesting appears in src/modules/agents/ui/components/agent-form.tsx and src/modules/meetings/ui/components/meeting-form.tsx where indentation reaches ten levels, making the control flow hard to trace. Repeated 6‑line blocks are present across auth and dashboard pages, indicating missing shared helpers.

How To Use It

# Clone the exact repo
git clone https://github.com/moses-y/meetai.git
cd meetai

# Install dependencies (npm is declared in package.json)
npm install

# Copy example environment and fill required keys
cp .env.example .env
# Edit .env: DATABASE_URL, OPENAI_API_KEY, STREAM_API_KEY, POLAR_API_KEY, etc.

# Apply database schema (Drizzle ORM)
npx drizzle-kit push

# Start the dev server
npm run dev

The dev server runs on http://localhost:3000. Authentication routes live under /auth/*, dashboard under /dashboard/*, and live calls under /call/[meetingId].

Real‑World Use

A SaaS provider could embed this repo as a white‑label meeting assistant. After configuring their own OpenAI and Stream keys, they would ship a branded version where each customer creates agents that automatically summarise calls and store transcripts in the provider’s PostgreSQL instance.

Code Health & Issues

Critical – next@15.3.2 is pinned to a version with a critical advisory (GHSA‑9qr9‑h5gf‑34mp). Upgrade to the patched release.
High – No LICENSE file; redistribution rights are undefined. Add MIT/Apache‑2.0.
High – No test suite. Introduce unit/integration tests for public entry points (src/db/index.ts, src/lib/email/index.ts).
High – No CI workflow. Add a GitHub Actions pipeline that runs npm run lint && npm run build && npm test.
Medium – Dependabot not configured. Add .github/dependabot.yml for npm and GitHub Actions.
Low – Repository conventions missing (.editorconfig, .gitattributes, formatter config). Add them to enforce consistent style.

Additional technical debt: deep nesting in agent/meeting forms, duplicated auth page logic, and an oversized sidebar.tsx component. Refactoring these will reduce cognitive load and lower the risk of regressions.

The Bottom Line

meetai offers a fully integrated AI meeting platform with modern Next.js and TypeScript tooling, but it ships with critical security, testing, and maintainability gaps. It is suitable for teams that can allocate effort to upgrade dependencies, add CI/CD, and refactor the identified high‑complexity modules before production use.

What the analyser found

Deployment readiness

4/7

Container image
CI pipeline
Lockfile committed
Test suite
README
License
No committed secrets

Composition

220 files

TSX130
TypeScript48
JSON8
SQL3
Markdown1
CSS1

ReactNext.js

Module dependencies

The 10 most depended-upon modules of 180, from static import analysis. Red outline marks a module in an import cycle.

graph LR n0_src_modules_meetings_types["types"] n1_s_hooks_use_meetings_filters["use-meetings-filters"] n2_nts_hooks_use_agents_filters["use-agents-filters"] n3_src_modules_agents_types["types"] n4_nts_ui_components_agent_form["agent-form"] n5_s_ui_components_meeting_form["meeting-form"] n6_src_trpc_routers__app["_app"] n7_src_modules_agents_schema["schema"] n8_src_modules_meetings_schema["schema"] n9_src_trpc_init["init"] n4_nts_ui_components_agent_form --> n3_src_modules_agents_types n4_nts_ui_components_agent_form --> n7_src_modules_agents_schema n1_s_hooks_use_meetings_filters --> n0_src_modules_meetings_types n5_s_ui_components_meeting_form --> n8_src_modules_meetings_schema n5_s_ui_components_meeting_form --> n0_src_modules_meetings_types n6_src_trpc_routers__app --> n9_src_trpc_init

Dependencies

20 of 101 declared dependencies are a major version behind. Resolved 101 of 101 against the registry.

Package	Declared	Latest	Behind
`@types/node`	^20	26.2.0	6 major
`nodemailer`	^7.0.3	9.0.5	2 major
`openai`	^5.8.2	7.4.0	2 major
`@types/nodemailer`	^6.4.17	8.0.1	2 major
`typescript`	^5	7.0.2	2 major
`@dicebear/core`	^9.2.2	10.6.0	1 major
`@tanstack/react-table`	^8.21.3	9.1.2	1 major
`dotenv`	^16.5.0	17.4.2	1 major

Findings

MediumNo CI/CD pipeline detected - no automated build/test gate .github/ or CI config
MediumNo LICENSE file - unclear usage/redistribution rights root

What would stop me shipping this

Ranked by severity × confidence × production reach. Reach is the honest discriminator across a collection that is mostly other people's code: the same finding matters more in something that ships.

critical1

high3

medium1

low1

Upgrade the pinned dependency carrying a critical advisorycritical31 occurrences

next@15.3.2 GHSA-9qr9-h5gf-34mp (critical) +30 more

The manifest pins the exact version the advisory covers, so this is not a warning about drift: the vulnerable code is what installs, and a critical rating means it is reachable over the network without credentials or user interaction.

Fix: Upgrade to the fixed version named in the advisory, then commit the lockfile.

Add a LICENSE; redistribution rights are undefinedhigh

no licence file at the repository root

Fix: Add MIT or Apache-2.0 at the repository root.

Add a test suite; this repository has nonehigh180 occurrences

180 source files, no test files

Any change ships with no signal that existing behaviour still holds, so a regression reaches production undetected.

Fix: Add one test per public entry point, then a CI step that runs them.

Add a workflow that builds and tests this repositoryhigh

180 source files, no CI configuration

Every change merges with nobody having run the build once, which across this estate is 499 repositories.

Fix: Add a workflow running the project build and test command on push and pull_request.

Enable Dependabot or Renovatemedium

1 manifest(s), no update bot configured

Without a bot a published advisory sits unpatched until someone audits by hand, which across 1,322 repositories means never.

Fix: Commit .github/dependabot.yml covering the repo ecosystems plus github-actions.

Add the repository convention files this project lackslow3 occurrences

missing .editorconfig, .gitattributes, a formatter config

Without them one contributor's editor writes tabs into a Python file, a shell script commits with CRLF and fails in the container, and a notebook diff is unreviewable.

Fix: Add .editorconfig, .gitattributes with text=auto eol=lf, and a formatter config.

Checked deterministically against the repository tree and a bounded set of its files: committed credentials, unpinned actions and base images, missing lockfiles and update bots, workflows that discard failures, published advisories against the declared dependencies, runtime configuration, licensing and notebook reproducibility. No language model is involved in this section.