Will It Vibe?Child process spawned from request input
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 25 points from that category, once per scan, no matter how many places it turns up.
What it detects
child_process exec/execSync/execFile/spawn is called with an argument taken from req.query/params/body/headers, so shell metacharacters in that input become command injection.
Why it matters
child_process exec and execSync hand a full command string to a shell, so any request value in it can inject extra commands with shell metacharacters like ; | && or backticks. That turns a filename or form field into arbitrary command execution on your server, one of the most severe bugs a web app can have. Even spawn is unsafe when the shell option is on or the binary is user-chosen.
How to fix it
Never build a shell command from request input. Use execFile or spawn with the binary fixed and arguments passed as a separate array (and shell disabled), so input is treated as data, not code. Validate any user-supplied argument against an allow-list. If you truly need shell features, restructure into multiple argument-list calls rather than interpolating input.
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