w3c / webappsec-fetch-metadata
Fetch Metadata
☆75Updated 6 months ago
Related projects ⓘ
Alternatives and complementary repositories for webappsec-fetch-metadata
- WebAppSec Content Security Policy☆210Updated 3 weeks ago
- A security/privacy review questionnaire for W3C specs☆25Updated 2 months ago
- WebAppSec Subresource Integrity☆70Updated 3 weeks ago
- WebAppSec Secure Contexts☆33Updated 11 months ago
- A Modest Content Security Proposal☆39Updated 3 years ago
- Client-Side Storage Partitioning☆71Updated last year
- ☆38Updated 2 years ago
- Opaque Response Blocking (CORB++)☆35Updated 2 years ago
- 🔒🔍 A Go package to scan sites against requirements for Chromium-maintained HSTS preload list.☆115Updated last month
- This is both a terrible and wonderful idea.☆10Updated 5 years ago
- Reporting API☆75Updated 2 months ago
- [On hold for now] A mechanism for origins to set their origin-wide configuration in a central location☆33Updated 2 years ago
- Discussion area for security aspects of ECMAScript☆64Updated 6 years ago
- Storage Standard☆125Updated 3 weeks ago
- WebAppSec Credential Management☆50Updated 2 months ago
- What is browser fingerprinting and how should specification authors address it.☆56Updated this week
- Signature-based Resource Loading Restrictions☆23Updated this week
- Secure Contexts, but with _more_ secureness!☆19Updated 6 months ago
- Problem statement and basic mitigations for ephemeral fingerprinting on the web.☆20Updated 3 years ago
- Cookies should take scheme into account, just like every other storage mechanism on the web.☆16Updated 4 years ago
- WebAppSec Referrer Policy☆26Updated last week
- W3C specs and API reviews☆332Updated 2 months ago
- Network Error Logging☆81Updated 2 months ago
- User Interface Security and the Visibility API☆11Updated 3 years ago
- ☆23Updated 3 years ago
- Web Application Security Working Group repo☆607Updated 2 weeks ago
- `document.domain` intentionally weakens the only security boundary we have. Perhaps we can dump it?☆16Updated last year
- A place to raise issues with the WHATWG Steering Group☆65Updated last week
- Suborigins☆25Updated 3 years ago
- Specification for the Client Hints infrastructure - privacy preserving proactive content negotiation☆61Updated 4 months ago