Add Subresource Integrity to the readme

[tvb]

SRI is a new W3C specification that allows web developers to ensure that resources hosted on third-party servers have not been tampered with. Use of SRI is recommended as a best-practice, whenever libraries are loaded from a third-party source.

It would be great to provide the sha256 hashes for each version in the readme

[SirRawlins]

Thanks for this suggestion too - sounds good, I shall take a look and see what we can do. 👍

…

On Wed, 19 Sep 2018, 21:02 Tristan, ***@***.***> wrote: SRI is a new W3C specification that allows web developers to ensure that resources hosted on third-party servers have not been tampered with. Use of SRI is recommended as a best-practice, whenever libraries are loaded from a third-party source. It would be great to provide the sha256 hashes for each version in the readme — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#61>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAtiK7si6_lfuoRT7aKiWTDe6k7-pVueks5ucqLTgaJpZM4Ww334> .

[tvb]

@SirRawlins any update?

[SirRawlins]

@tvb I did take a look at this, but the current grunt-sri tool we'd want to drop in looks a little limited, and outdated. Would be great to get this added but for the moment it's not a high priority.

I'm going to leave the issue open though, as don't want to forget about it. 😄

[tvb]

@SirRawlins did you perhaps forget about it still? 😇