No structured logging
Part of Testing & CI, which counts for 10% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
No logging library (winston/pino, or Python's logging module) was detected -- production issues will be hard to diagnose with only console.log/print.
Why it matters
console.log and print give you untimestamped, unleveled, unfilterable output; in production you cannot separate a real error from debug noise or follow what happened to a single request. When something breaks at 2am, structured logs with a level, a timestamp, and context fields are the difference between minutes and hours of diagnosis. Adding them before the first incident is much cheaper than during it.
How to fix it
For Node, add pino (fast, JSON output by default): create one shared module like src/lib/logger.ts exporting a configured instance, then replace console calls in server-side code, starting with error paths and request handlers where diagnosis matters most. For Python, the stdlib logging module is enough: configure it once at startup (logging.basicConfig or dictConfig with the level read from an environment variable) and use logging.getLogger(__name__) per module. Log context as structured fields (user id, request id, error object), not string concatenation.
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