Even if there is no practical impact, there is a maintenance impact. Think of yourself a few years on or a new team member. Some innocent refactoring occurs, an

Even if there is no practical impact, there is a maintenance impact. Think of yourself a few years on or a new team member. Some innocent refactoring occurs, and the service is deployed as public-facing. Every time your code is scanned, someone has to consciously ignore it. That can lead to alert fatigue. What if it gets squelched? Now the code has dangerous debt. Mentally, there is toil: this place in the code is fine, but what about others? A conscientious dev will start looking for similar issues. That takes up more time. Suppose someone searches the codebase for SQL examples and finds this one. They think it's an acceptable pattern, even though the search also turns up parameterized queries. Now the bad precedent repeats in the shiny new service, and debt proliferates.