Repository navigation
Add nonce CSP, framing protection, and security.txt - #78
Merged
Merged
Conversation
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.
Changes
Production HTML now receives a per-request nonce CSP,
frame-ancestors 'none', andX-Frame-Options: DENYthrough the existing TanStack server wrapper, including 404 and fallback error responses. Lovable preview hosts permit self and the Lovable editor through CSP, with SAMEORIGIN as the legacy framing fallback. HTML uses no-store to prevent nonce reuse.The nonce flows through TanStack/React streaming, hydration, and JSON-LD. Script policies avoid unsafe-inline and unsafe-eval. Allowlists cover this app's Supabase project, Stripe embedded checkout, Cloudflare challenges, Google Fonts, and Lovable OAuth; Flock scripts and analytics are same-origin. Inline styles remain allowed for React/Radix/charts. The fallback retry link no longer needs an inline script handler.
Adds RFC 9116
/.well-known/security.txtas a public file plus an explicit plain-text route for hosts that skip dot-directory assets. Uses contact@zeroagency.ai from SECURITY.md; expires 2027-04-28.Validation
/.well-known/security.txtreturns 200 and text/plain with the expected document.vite previewhas an existing output-path mismatch; validated with local Wrangler instead.No deployment/publication or Lovable AI credits used. Live HTTP behavior remains unchanged until this PR is merged and deployed separately. Authenticated checkout/OAuth flows were inspected in source but not transacted end to end.