• Hello AddToAny Team,

    We’re using the AddToAny Share Buttons WordPress plugin, and during our security scans, the externally loaded script below is consistently flagged for missing Subresource Integrity (SRI):

    <script id="addtoany-core-js" defer="" src="https://static.addtoany.com/menu/page.js">
    <script type="text/javascript" defer="" src="https://static.addtoany.com/menu/page.js" id="addtoany-core-js">

    We understand that page.js is served from your CDN and is updated dynamically, which makes using a static SRI hash impractical because any update would invalidate the hash and prevent the script from loading.

    Could you please advise if there are any plans to support SRI in the future? For example:

    Providing versioned JavaScript files with published SRI hashes.
    Offering a self-hosted version of page.js for environments with strict security requirements.
    Any other recommended approach for organizations whose security policies require SRI for all external JavaScript resources.

    We also noticed your documentation on supporting CSP nonces, which is helpful for Content Security Policy. However, CSP nonces do not address security scanners that specifically require SRI.

    Any guidance or roadmap regarding SRI support would be greatly appreciated.

    Thank you!

Viewing 1 replies (of 1 total)
  • Plugin Author micropat

    (@micropat)

    Similar to Google Tag Manager and other scripts, SRI isn’t applicable to AddToAny’s evergreen script, so you can safely ignore a scanner’s overly broad advice on SRI in this instance.

    Exactly as you found, AddToAny supports a strict Content Security Policy with nonces as in the CSP demo.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.