One or more external scripts are loaded without a Subresource Integrity (SRI) hash, exposing users to supply-chain attacks.
By Seoxpert Editorial · Published
Without SRI, browsers cannot verify the integrity of third-party scripts, leaving users vulnerable if a CDN is compromised. This can lead to security breaches, loss of user trust, and potential SEO penalties if malicious code is injected. Implementing SRI is a simple, effective way to protect your site and users.
Leaving this unresolved exposes your site and users to supply-chain attacks via compromised third-party scripts.
Automated crawlers scan for <script> tags with cross-origin URLs missing the 'integrity' attribute.
Problem: Script without SRI
<script src="https://cdn.example.com/lib.js"></script>Fix: Script with SRI and crossorigin
<script src="https://cdn.example.com/lib.js" integrity="sha384-BASE64HASH" crossorigin="anonymous"></script>SRI allows browsers to verify that a fetched script matches a known hash, protecting against compromised third-party resources.
Download the script and run 'openssl dgst -sha384 -binary lib.js | openssl base64 -A' to get the hash, then add it to the 'integrity' attribute.
Yes, any change to the script requires regenerating and updating the SRI hash.
You can, but you'll need to update the hash with every script change or use versioned URLs to manage updates.
While not a direct SEO ranking factor, compromised scripts can harm user security and trust, indirectly impacting SEO.
Run a scan to see if Cross-Origin Scripts Missing Subresource Integrity (SRI) affects your pages.
Scan my website →