Add Content-Security-Policy and security headers to Vercel deployment#11
Draft
Add Content-Security-Policy and security headers to Vercel deployment#11
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: pc-style <134572227+pc-style@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add Content Security Policy header configuration
Add Content-Security-Policy and security headers to Vercel deployment
Feb 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Critical security issue: CSP header not set on https://pcstyle.dev, leaving the site vulnerable to XSS and data injection attacks.
Changes
CSP header configured in
vercel.jsonwith whitelisted domains:cdn.tailwindcss.com,esm.shfonts.googleapis.com,cdn.tailwindcss.comfonts.gstatic.comog.pcstyle.devframe-ancestors 'none',base-uri 'self',form-action 'self'Additional security headers:
X-Frame-Options: DENYX-Content-Type-Options: nosniffReferrer-Policy: strict-origin-when-cross-originPermissions-Policy: camera=(), microphone=(), geolocation=()Implementation
{ "headers": [ { "source": "/(.*)", "headers": [ { "key": "Content-Security-Policy", "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.tailwindcss.com https://esm.sh; ..." } ] } ] }Note:
unsafe-inlineandunsafe-evalrequired for Tailwind CDN. Migrating to build-time Tailwind would eliminate this but requires architecture changes beyond scope.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.
Summary by cubic
Adds a Content Security Policy (CSP) and standard security headers to harden the app. The policy whitelists our CDNs (Tailwind, Google Fonts, esm.sh, og.pcstyle.dev) so fonts/icons load consistently without regressions.
Written for commit af57eff. Summary will update on new commits. Review in cubic