Hi @Danil42Russia, thanks for opening an issue.

I'm hesitant to add this for two reasons:

1. IME, making it easy to de facto disable audits means people leave them disabled, even when they only mean to disable them temporarily.
2. Users can already de facto do this by using one of the machine readable output formats (JSON or SARIF) and filtering the results from there.

Does (2) work for your use case?

Yes, I chose the second option, but the error message is a bit depressing :( . I prefer the output in plain format for local work to json :D

In principle, I agree with your arguments as to why this should not be done (although I would add a ban on this flag if there is a CI environment variable, but it's a good thing I'm not the author xD).

It seems worth mentioning this point in the documentation; it certainly won't be superfluous.

P.S. I needed this to start sorting out the problems, because right now there are 355 findings (112 suppressed, 42 fixable): 7 informational, 35 low, 28 medium, 173 high D: And I wanted to start fixing them by correcting each individual rule and gradually getting to 0 warnings.

Yeah, it's kind of unfortunate that the plain format can't easily be filtered. I definitely see the value in that, especially for incremental fixes.

I'm going to convert this into a discussion since this is something I'm interested in, but don't have a clear design/picture for yet.