Features
Everything you need to understand any codebase
Health Check
Get a health score (0-100) and letter grade for any project. Detects missing linting, formatting, tests, and security issues.
Security Scanning
Catches committed secrets, exposed .env files, and private keys before they reach production.
Auto-Fix
One command to set up ESLint, Prettier, Vitest, and EditorConfig with sensible defaults. No manual configuration.
Architecture Diagram
Generates an ASCII architecture map showing your project's layers: frontend, API, services, and database.
CI/CD Health Gate
Use projscan ci to enforce health standards in your pipeline. Exits with code 1 if the score is too low.
Baseline Tracking
Save a health baseline and compare over time. Track whether your project is improving or degrading.
See it in action
A closer look
Project Health Report
Run projscan doctor to get an instant health check. See your score, detected errors, and actionable recommendations, all in milliseconds.
Directory Structure
Visualise your project's file tree with per-directory file counts. Instantly understand the layout of any codebase you're onboarding to.
Architecture Diagrams
Automatically detect architectural layers from your directory structure and frameworks. See frontend, API, services, and database layers at a glance.
Dependency Analysis
Break down production vs. development dependencies. Flag wildcard versions, excessive counts, and missing lock files.
CI/CD Integration
Gate your pipelines with projscan ci. Set a minimum score threshold. If the project doesn't meet it, the build fails. Clean output designed for CI logs.
File Explanation
Point ProjScan at any file to understand its purpose, imports, exports, and potential issues. All using local static analysis: no AI, no network calls.
About
Why ProjScan?
ProjScan was born from the repetitive friction of onboarding to new codebases. Every time you clone a repo, whether it's a client project, open-source contribution, or your own code from six months ago, you spend 10-30 minutes poking through config files to answer the same questions. What's the stack? Are there tests? Is there linting? Are there any obvious issues?
ProjScan answers all of this in a single command. It runs entirely locally with zero network requests, scans thousands of files in under 2 seconds, and has just 4 runtime dependencies. It's designed to be fast enough to run on every save or as a pre-commit hook.
App Details
Scan any codebase in seconds
No install required. Run with npx.
npx projscan
Get Started