No CI configuration
Part of Testing & CI, which counts for 10% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
No continuous-integration config (GitHub Actions, GitLab CI, CircleCI, Travis) was found, so nothing runs checks automatically on push/PR.
Why it matters
Without CI, checks only run when someone remembers to run them locally, so a broken build or failing test can sit on the main branch for days while everyone pulls it. CI runs the same checks on every push and pull request automatically, which also gives you a deploy gate: code that fails never reaches production. For a solo or AI-assisted project it is often the only reviewer that shows up every time.
How to fix it
Add a GitHub Actions workflow at .github/workflows/ci.yml (or the GitLab/CircleCI equivalent if that is where the repo lives) triggered on push and pull_request. The job should check out the code, set up Node or Python at your version, install dependencies with the lockfile (npm ci / pip install -r requirements.txt), and run whichever of lint, typecheck, and test commands the project actually has. Use the setup action caches (actions/setup-node with cache: npm) so runs stay under a couple of minutes.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo