Change of vulnerability warnings

[YvoTuk]

On itself, the vulnerability warnings are a great feature as it also helped me to realize I made a mistake in my setup.

However, it would be good to change the routing slightly in such a way that the user can choose to ignore a specific vulnerability.

For instance: I’m using a credential_secret in node-red which is marked as vulnerability, but reality is… it’s not really.
From what I understand changing the credential_secret may cause some issues with the flows which I’ve made, so I’d rather not and feel confident it’ll never be an issue.

What I would like to is to have an option to permanently ignore that specific vulnerability.

[Burningstone]

There’s already a feature requrst for opting out of the insecure password warning.

Opt~out/in Password check to third party

For the record, sending data to a third party is not the only concern. Many users would like to opt out to prevent the hourly nag and the additional overhead and logging caused by all this checking. This is not a function which everyone needs, and certainly not a function which anyone needs hourly.

Please use the search before creating a new feature request.
@tom_l can you pleae close this?