Feature: score + api

[barryvdh]

It would be nice to have some sort of 'score' to the results and a total score. For example, passed rule = 10 points, notice 9, warning 7, error 4, critical 0. Then sort the results in order of lowest score (most critical on top) and calculate the total score percentage to give the website a score.

That score could be also used to automate it a bit for an Api, eg call it with a list of rules, use a down to check them periodically, integrate with other services etc.

[phanan]

This is such a good idea. Thing is, though, there are certain rules that don't apply to everyone, e.g. Google Analytics. How do we count this toward the score?

[barryvdh]

You only count the rules that are enabled in the configuration.

[phanan]

Yeah but GA is enabled by default. At least currently.

…

On Mon, Mar 6, 2017 at 1:29 PM, Barry vd. Heuvel ***@***.***> wrote: You only count the rules that are enabled in the configuration. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHrt0mKHBDWxiFTMocvgz6g1zwG8KOxnks5ri6evgaJpZM4MR7Wb> .

[m1guelpf]

Maybe you could assign it a LEVEL error notice, so it doesn't cost points...
Or you could run only the rules specified in a POST request...

[m1guelpf]

@barryvdh @phanan Any updates on this?

[barryvdh]

Instead of the percentage, we could use an 'impact' value, like Google Pagespeed Insights does.

Passed: 0 (no impact), Notice: 1, Warning:10, Error: 25, Critical: 100 (or something)

Or you could say that a Notice is optional, and doesn't have impact. Or create an 'Optional' rule.

Then instead of the percentage, add the 'impact' you could have by following all the rules.

In some cases you could thinkg about specifying an impact directly in the Rule, if you want to be more specific.

Then the impact can also be used to sort the rules.