AI Chaos Index: 87/100
CRITICAL
This is a real AI-generated SaaS dashboard — built with Cursor in a few sessions. It works. It runs. But structurally, it's a ticking time bomb.
ACI 87/100 — Critical zone. Architecture intervention required.
1,084 LOC in a single frontend file. 0% test coverage. No CI/CD.
Every change risks breaking unrelated functionality. Onboarding a new developer is extremely costly.
Score above 75 = Critical. Architecture intervention required before scaling.
Project Overview
Root Cause Severity Breakdown
1,084 LOC single-file monolith. All UI + logic + state in one component.
Overlapping util files. No shared types between frontend and backend.
No README, no docs, mixed naming conventions, no .env.example.
Zero tests. No testing framework installed. All 8 files untested.
No CI/CD. No pre-commit hooks. No branch protection. No quality gates.
Top Findings
Monolithic Frontend (page.tsx = 1,084 LOC)
The entire application UI, state management, and business logic lives in a single React component file. Any change risks breaking unrelated functionality.
Risk: Every feature addition becomes exponentially harder. With 1,084 LOC in one file and zero tests, regression risk is significantly harder to control.
Zero Test Coverage
No tests exist anywhere. No testing framework is even installed. There is no way to verify changes don't break existing functionality.
Risk: Production deployments are blind — you have no way to catch regressions before users do. This is a leading cause of failure in AI-built apps after launch.
No CI/CD or Deployment Safety Net
Code goes directly from development to production without any automated checks, linting, or testing gates.
Risk: A single typo or broken import can take down production. No rollback mechanism exists.
Backend API Monolith (api.py = 619 LOC)
All routes, business logic, data access, and validation in a single file with no separation of concerns.
Risk: Adding new API endpoints becomes increasingly risky. Security vulnerabilities are harder to spot.
No Documentation or Architecture Records
No README, no architecture docs, no API documentation. A new developer would need to reverse-engineer the entire application.
Risk: Onboarding cost is extremely high. Knowledge is trapped in chaotic code.
Download the Sample Report
See exactly what you get with a Quick Scan — the full PDF report for this analysis.
Download PDF Report (ACI 87)PDF • 5 pages • AI Chaos Index Quick Scan Report
Is your app in a similar state?
Get your AI Chaos Index score in 24 hours. Know exactly where you stand.