<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Codepen on CSP Guide</title>
    <link>https://csp-guide.com/tags/codepen/</link>
    <description>Recent content in Codepen on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 02 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/codepen/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for CodePen Embeds: Options, Tradeoffs, and Fixes</title>
      <link>https://csp-guide.com/posts/csp-for-codepen-embeds/</link>
      <pubDate>Sun, 02 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-codepen-embeds/</guid>
      
      <description>&lt;p&gt;CodePen embeds look harmless until your CSP starts blocking them.&lt;/p&gt;
&lt;p&gt;That usually happens the first time you paste CodePen’s embed script into a site with a reasonably locked-down policy. Suddenly the pen doesn’t render, the console fills with CSP violations, and you’re stuck deciding whether to weaken your policy or drop the embed.&lt;/p&gt;
&lt;p&gt;I’ve had to make this tradeoff a few times. The short version: if you want CodePen on a production site, the safest path is almost always the iframe embed, not the JavaScript embed. The rest of the guide is about why.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
