w3c / webappsec-fetch-metadataLinks
Fetch Metadata
☆75Updated 9 months ago
Alternatives and similar repositories for webappsec-fetch-metadata
Users that are interested in webappsec-fetch-metadata are comparing it to the libraries listed below
Sorting:
- WebAppSec Content Security Policy☆221Updated 2 months ago
- WebAppSec Subresource Integrity☆78Updated 6 months ago
- WebAppSec Secure Contexts☆37Updated 11 months ago
- Web Application Security Working Group repo☆653Updated last month
- W3C specs and API reviews☆359Updated last month
- Storage Standard☆141Updated last month
- A Modest Content Security Proposal☆40Updated 4 years ago
- This is both a terrible and wonderful idea.☆12Updated 6 years ago
- Signature-based Resource Loading Restrictions☆44Updated 4 months ago
- A mechanism to selectively enable and disable browser features and APIs☆416Updated 3 months ago
- A security/privacy review questionnaire for W3C specs☆29Updated last month
- Specification for the Client Hints infrastructure - privacy preserving proactive content negotiation☆62Updated last year
- Opaque Response Blocking (CORB++)☆36Updated 3 years ago
- Client-Side Storage Partitioning☆93Updated 2 years ago
- A place to raise issues with the WHATWG Steering Group☆73Updated 3 months ago
- Discussion area for security aspects of ECMAScript☆64Updated 8 years ago
- Geolocation Sensor☆62Updated last year
- Web security drafts☆32Updated 6 years ago
- WebAppSec Referrer Policy☆27Updated 3 months ago
- Parse Content Security Policy headers, warn about policy errors, safely manipulate, render, and optimise policies☆72Updated last month
- Network Error Logging☆89Updated this week
- Permissions API☆108Updated 3 months ago
- [On hold for now] A mechanism for origins to set their origin-wide configuration in a central location☆33Updated 3 years ago
- ☆173Updated last month
- ☆259Updated last month
- Cookies should take scheme into account, just like every other storage mechanism on the web.☆16Updated 5 years ago
- How we track participants in the WHATWG☆40Updated this week
- `document.domain` intentionally weakens the only security boundary we have. Perhaps we can dump it?☆17Updated 2 years ago
- MIME Sniffing Standard☆117Updated 5 months ago
- ☆40Updated 5 months ago