Code Health Monitor
Run an on-demand technical health report on any project — code style, syntax, builds, dependencies, and a single health score — right inside the IDE, and export it as a PDF.
The Code Health Monitor gives any project a quick, on-demand technical checkup. It scans your code and environment, runs a set of quality checks, and rolls everything up into a single health score — so you can see at a glance how production-ready a generated app is.
It's read-only and free: running a report never changes your code and never consumes credits.
Opening the report
- Open a project in the IDE
- Click the Code Health tab in the top navigation bar
- The scan runs automatically and the report appears in a minute or so
Each report is generated live — nothing is stored. Use Re-scan in the header to force a fresh analysis, or Download PDF to save a copy.
A report can take up to a minute to generate. Results are cached for about 15 minutes, so re-opening the tab is instant — click Re-scan when you want fresh results. Downloading the PDF always runs a fresh scan.
The health score
The headline number is a score from 0 to 100 — the percentage of applicable checks that passed. Checks that don't apply to your stack are excluded from the calculation.
| Score | Label |
|---|---|
| 80–100 | Excellent |
| 65–79 | Good |
| 50–64 | Fair |
| 0–49 | Poor |
If no checks could run, the score shows as Not measured.
What the report includes
The report is organised into several sections:
| Section | What it shows |
|---|---|
| Technology Stack | Laravel version and the detected frontend stack (Blade, Livewire, React, or Vue) with versions |
| Project Overview | PHP, Node, and npm versions, environment, and creation / last-activity dates |
| Codebase | Counts of routes, controllers, models, migrations, database tables, and tests, plus total PHP files, lines of code, and the largest file |
| Quality Checks | The pass/fail checks described below |
| Security | Flags risky settings such as APP_DEBUG enabled in production or a missing APP_KEY |
| Dependencies | Full lists of Composer and npm packages (production and dev), with versions |
Quality checks
Each check reports a status and, where relevant, the specific files involved:
| Check | What it verifies |
|---|---|
| PHP syntax | Runs php -l across app/, routes/, database/, and config/ — fails if any file has a syntax error |
| Code style | Runs Laravel Pint and reports files that don't match the project's style rules |
| Tests | Runs the project's PHPUnit / Pest suite and reports the total and failing counts |
| Production build | Runs npm run build and checks it completes successfully |
| JavaScript lint | Runs ESLint and reports the number of problems found |
A check shows Not applicable when it doesn't fit your project. The production build and JavaScript lint checks only run for React and Vue projects — Blade and Livewire projects skip them. The tests check only runs when the project has a test suite that can be executed.
Running vs. stopped projects
The scan adapts to whether your project container is running:
- Project running — all checks run inside the container, including the production build and test suite.
- Project stopped — read-only checks (PHP syntax, code style, file counts, dependencies) still run against your stored files. Checks that need a live environment, like the production build and tests, are skipped.
If you want the most complete report, click Run to start the project first, then open the Code Health tab and re-scan.
Exporting a PDF
Click Download PDF in the report header to save the full report as an A4 PDF, named code-health-<project>-<date>.pdf. The PDF contains the same sections as the on-screen report and is handy for sharing a project's status or keeping a record.
Troubleshooting
| Problem | Solution |
|---|---|
| "The scan timed out. Please try again." | The analysis exceeded its time limit — click Re-scan to retry. Large projects can occasionally time out. |
| Health score shows Not measured | No checks could run — usually because the project container is stopped and no stored files were found. Start the project and re-scan. |
| Build / test checks show Not applicable | These require a running project (and, for the build, a React or Vue stack). Start the project and re-scan. |
| A note says analysis ran on stored files | The project wasn't running, so live checks were skipped. Start the project and re-scan to include them. |