Portal

code_pattern

Severity: warn. A risky code pattern was found.

What Kaviris saw

A rule matched a pattern that often leads to security holes, for example running code built from request data (eval, new Function), a framework's debug mode left on, or a query built by pasting strings together. The location names the file and line.

What happens

The deploy goes on; this is a warning.

How to fix it

Look at the file and line. Typical fixes: parse data instead of evaluating it, turn debug mode off in production, use your database library's query parameters. Ask your agent: "fix the code_pattern warning at server.js:42".

All refusal codes

This page as Markdown