Flusk Vault

On Database rating tool the table names are unsorted at first time. They only appear in alphabetic order after the table fields are rated.

Ignoring an issue should not be used to sweep it under the rug. Especially since these ignored issues appear on the certificate. So it would be helpful if we could add a comment when ignoring an issue. A comment which would also appear in the report. This would make it possible to justify this choice on the certificate, and it would help to question it later if the circumstances have changed.

For the analytics, it would add quite a bit of value to know the views per page (url parameters, paths, etc.). A heatmap of interactions would be the cherry on top of the cake.

Identify the performance impact (extra page load seconds) for every plugin on both pages where the plugin is installed or not.

This is one of the most common mistakes among big apps, and it does take quite some time and maintenance to keep updating the database connections as well as pages workflows into a visual documentation for a bigger dev team.

It would probably be nice to be able to define alerts for when an app reaches 90% (or any value) of the current WU included in the app's plan.