Your code deserves a regular checkup.
Catch issues before they become problems.
From exposed secrets to broken configurations, cDoc examines your project, finds potential problems and tells you exactly where to start fixing them. All from your terminal.
Open sourceDeveloper-firstLocal-first
Live demo
One command. Real output.
Illustrative terminal output. Actual results will depend on the project scanned and checks implemented.
Everything looks fine. Until it doesn’t.
A missing environment variable, an exposed API key or an outdated dependency can turn an otherwise good project into a frustrating debugging session.
The problem isn’t always that developers don’t care. Sometimes, they simply don’t know what they’re missing.
Hidden problems
Issues quietly sitting in your codebase, waiting for the worst possible moment to show up.
Configuration headaches
Missing environment variables, incomplete scripts and configurations that don’t quite add up.
Security blind spots
Sensitive credentials and files that shouldn’t be exposed or committed.
Meet cDoc. Your project's first line of diagnosis.
cDoc gives your codebase a structured health check without making you dig through dozens of files manually.
Run a scan, see what needs attention and get practical recommendations to help you fix it.
Everything you need to spot the warning signs.
Security checks
Find potential exposed credentials, suspicious hardcoded secrets and risky file configurations before they become bigger problems.
Know what’s exposed. Know what needs attention.
Dependency health
Examine your project’s dependencies, identify inconsistencies and discover packages that may need attention.
Keep your dependencies in check.
Environment validation
Check environment configuration and spot missing variables or incomplete example files.
No more guessing what your project needs.
Project health reports
Get an organised overview of your findings, severity levels and recommended next steps.
Turn scattered problems into a clear action plan.
Three steps to a healthier codebase.
- 01
Install cDoc
Add cDoc to your development workflow using npm.
npm install -g @oluwat0s1n/devdoctorInstalls the CLI globally.
- 02
Run your checkup
Navigate to your project and let cDoc examine its configuration.
cdoc scanScans the project in your current directory.
- 03
Review. Fix. Ship.
Understand your findings, follow the recommendations and get back to building.
No configuration required.
No more digging around. Just clear answers.
cDoc doesn’t just flag problems. It helps you understand what went wrong, where to look and what to do next.
Illustrative terminal output. Actual results will depend on the project scanned and checks implemented.
Project health
- Project configurationpassed
- Dependenciespassed
- Environment variablesattention
- Git configurationattention
- Security checkspassed
2 findings need attention.
Your next steps are ready.
Your codebase isn’t ours to collect.
cDoc is designed to run locally. Your project files stay on your machine, and the initial diagnostic experience doesn’t require an account or send your source code to an AI service.
You stay in control of what gets scanned, what gets reported and what gets changed.
- No account required.No sign-up, no dashboard, no API key to manage.
- Local-first diagnostics.Scans run on your machine, against your files.
- No automatic file modifications.cDoc reports. You decide what changes.
Network-dependent checks will be explicitly opt-in.
Good tools get better when developers build together.
MIT licensedCommunity drivenOpen source
Run your first checkup.
npm install -g @oluwat0s1n/devdoctorInstall the CLI globally.
npx @oluwat0s1n/devdoctor scanOr run a scan without installing anything.
cdoc scanRun your first checkup inside a project.
Requires Node.js 20 or newer. Works on macOS, Linux and Windows.
Before you run your first checkup.
cDoc is an open-source command-line tool that scans JavaScript and TypeScript projects for common security, configuration, dependency and environment issues.
Give your codebase the checkup it deserves.
Find the issues. Understand the risks. Build with confidence.
Open source. Developer-first. Built for better code.