CODYGIENE

Troubleshooting

Common issues

"No files found to analyze"

CODYGIENE found no supported source files. Check:

  • You're in the right directory
  • The project has .js, .ts, .tsx, .jsx, .mjs, .cjs, or .sql files
  • Files are not all excluded by .codygieneignore or default exclusions

"PARTIAL scan" warning

Some eligible files were skipped. Check the coverage section for the reason. Common causes:

  • --max-files was used (intentional partial scan)
  • Parse failures in malformed files (check parseFailures in JSON output)
  • Files skipped due to size or encoding issues

Scores from a PARTIAL scan are not representative of the full repository.

Too many findings in terminal output

The terminal shows a prioritized subset. Low-priority findings are clustered by rule. To see all findings individually:

codygiene scan --format json -o report.json

Node.js version error

CODYGIENE requires Node.js 20 or later. Check your version:

node --version

Upgrade from nodejs.org if needed.

Invalid configuration

If .codygiene.json is invalid, CODYGIENE reports the problem and the file path. Check the JSON syntax and supported keys in Configuration.

Permission denied

CODYGIENE needs read access to your project files and write access to the output file (if using -o). Check file permissions.

Ctrl+C during scan

Interrupting a scan with Ctrl+C exits the process. No partial results are saved. Re-run the scan to get complete results.

Debug mode

For diagnostics:

codygiene scan --debug

Debug output goes to stderr and includes:

  • Files analyzed
  • TS source files
  • SQL migrations
  • Route handlers
  • Database tables
  • Auth signals
  • Enabled rules
  • Skipped rules

Debug mode does not include source content or snippets.

Getting help