Continuous Monitoring of npm audit results about cacti HOT 1 CLOSED

Update 1: Decided against tying CI success to the audit outcome because it would just make it flaky and often impossible to fix since patches don't get rolled out immediately for all the vulnerabilities.
A contribution should still be acceptable if it has some npm audit issues that we can fix later on. The reasoning behind that is that the npm audit outcomes are fluid and time dependent so trying to mandate a positive outcome for npm audit is futile and does not itself guarantee the software to be secure, in fact the opposite is a well known secret: all software is insecure until proven otherwise (and the latter has been proven to be impossible in general).

So with all that in mind, retiring this issue.

from cacti.