WICG / csp-nextLinks
A Modest Content Security Proposal
☆40Updated 4 years ago
Alternatives and similar repositories for csp-next
Users that are interested in csp-next are comparing it to the libraries listed below
Sorting:
- This is both a terrible and wonderful idea.☆12Updated 6 years ago
- Secure Contexts, but with _more_ secureness!☆20Updated last year
- WebAppSec Content Security Policy☆221Updated last week
- Custom ESLint rule to disallows unsafe innerHTML, outerHTML, insertAdjacentHTML and alike☆236Updated last month
- Fetch Metadata☆75Updated 6 months ago
- Cookies should take scheme into account, just like every other storage mechanism on the web.☆16Updated 5 years ago
- `document.domain` intentionally weakens the only security boundary we have. Perhaps we can dump it?☆17Updated last year
- Security contract types☆60Updated 3 years ago
- ☆11Updated 3 years ago
- Discussion area for security aspects of ECMAScript☆64Updated 7 years ago
- Opaque Response Blocking (CORB++)☆36Updated 3 years ago
- ☆251Updated last week
- A browser API to prevent DOM-Based Cross Site Scripting in modern web applications.☆636Updated this week
- ☆23Updated 3 years ago
- ☆370Updated 8 months ago
- [On hold for now] A mechanism for origins to set their origin-wide configuration in a central location☆33Updated 3 years ago
- Incrementally better HTTP state management.☆301Updated 3 years ago
- Test Page for HTTP/2 prioritization (server and browser)☆109Updated 5 years ago
- Network Error Logging☆89Updated 5 months ago
- TC39 proposal for mitigating prototype pollution☆50Updated 2 years ago
- What if developers could opt-into better default behaviors en masse, forcing them to pick and choose the legacy risks they want to enable…☆19Updated 2 years ago
- Signature-based Resource Loading Restrictions☆41Updated 2 months ago
- ☆75Updated 10 months ago
- Post-Spectre Web Development☆18Updated 2 years ago
- Log all the CSP violations!☆57Updated 2 years ago
- Web Application Security Working Group repo☆645Updated last week
- Parse Content Security Policy headers, warn about policy errors, safely manipulate, render, and optimise policies☆72Updated last year
- Archived proposal from 2018. Perhaps the approach in mikewest/scheming-cookies will be more successful!☆51Updated 5 years ago
- Make it easy to probe the strengths and weaknesses of a hardened Node.js stack☆19Updated 6 years ago
- rewrite constructor arguments, call DOMPurify, profit☆71Updated last year