DavidWells / DavidWells/analytics

Support for Content-Security-Policy "nonce" pattern

Open
#235 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.7k
Forks
267
PR merge metrics
No merged PRs in 30d

Description

An impermissive Content-Security-Policy is an important part of browser-based web security. For manual applications of third-party scripts (eg GA and FB), the simple addition of a nonce attribute to the script tag allows you to avoid adding overly permissive rules like 'unsafe-eval' or 'unsafe-inline' to your CSP.

If this feature already exists and I'm just missing it, (sorry, and) maybe consider this an issue to add it to the docs. If not, this is a request to add the ability to utilize existing APIs to add a string nonce to the attributes of the resulting script tags.

Thanks for your consideration!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Inspect the existing APIs for manually adding third-party scripts and the documentation describing script-tag attributes; the work is done when callers can provide a nonce and the resulting script tags include it without requiring permissive CSP rules.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.