Several third-party security rating tools (e.g., SecurityScorecard) flag published Framer sites for "Unsafe Implementation of Subresource Integrity" because the scripts Framer's platform injects automatically don't include integrity/crossorigin attributes. This includes things like:
These are emitted by Framer's own publishing pipeline, so site owners have no way to add SRI attributes ourselves. The Custom Code panel only lets us inject scripts we author, not modify what Framer itself outputs.
This is becoming a real business problem, not just a cosmetic scan finding: security ratings like SecurityScorecard are increasingly used by companies during vendor/procurement due-diligence, and this specific finding has already come up as a concern from prospective customers evaluating sites built on Framer. It reflects on Framer's platform for every site built on it, so a fix here would benefit the whole customer base, not just individual sites.
A few things that would help:
  1. Adding SRI hashes to platform-served scripts where the content is stable enough to support it.
  2. For dynamic/frequently-updated assets where a fixed hash isn't practical (e.g., bundle files that change on every publish), some official guidance on how customers should represent/respond to this finding in security reviews would be useful.
  3. Visibility into whether this is already on a roadmap. Happy to be pointed to an existing thread if this has been raised before.
Given how commonly this shows up in vendor security scans, I'd expect other Framer customers are hitting the same friction with their own customers/partners. Would appreciate this getting prioritized or at least acknowledged with a public status.
Thanks,