PythonIreland / PythonIreland/2026.pycon.ie
Security: CSP allows 'unsafe-inline' for scripts and styles
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 0
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
Problem
The CSP includes script-src 'self' 'unsafe-inline' use.typekit.net ... and style-src 'self' 'unsafe-inline' .... Not an SEO ranking factor, but 'unsafe-inline' weakens XSS protection. (The rest of the header set is excellent: HSTS, nosniff, X-Frame-Options DENY, Referrer-Policy, Permissions-Policy.)
Fix
Move to a nonce/hash-based CSP for the inline Typekit loader; optionally add preload to HSTS.
Files: netlify.toml / static/_headers
Found by /seo audit (technical), 2026-05-29.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the CSP definitions in netlify.toml and static/_headers, then locate how the inline Typekit loader is served. Determine how a nonce or hash can be applied without weakening the existing policy, and verify that the resulting headers no longer require 'unsafe-inline' for scripts or styles. Consider the optional HSTS preload separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100