w3c/webappsec-cspee Issues

Last updated Dec 22, 2024, 5:57:14 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

20 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time past SLO
#1	How is CSPEE recursive?	❌	6.2 years	6.2 years
#2	Embedded: make clear that servers MUST respond with a CSP or Allow-CSP-From header, <meta> CSP's are not allowed.	❌	6.2 years	6.2 years
#3	Embedding-CSP header	❌	6.2 years	6.2 years
#4	Embedded: consider other contexts other than iframe	❌	6.2 years	6.2 years
#5	Clarify what is the threat model for embedded enforcement	❌	6.2 years	6.2 years
#6	Embedded Enforcement: Invalid required csp attribute on iframe	❌	6.2 years	6.2 years
#7	Embedded: Think about the implications of allowing injected `csp` with reporting.	❌	6.2 years	6.2 years
#9	Fix subsume-source-expressions algorithm	❌	4.6 years	4.6 years
#10	Should file and filesystem schemes allow blanket enforcement?	❌	4.6 years	4.5 years
#11	Cancel navigation on invalid required CSP attribute	❌	4.5 years	4.5 years
#12	Should we restrict CSPEE to secure schemes?	❌	4.5 years	4.5 years
#13	Fix examples involving wildcard host matching.	❌	4.5 years	4.5 years
#14	Wildcard hosts and CSP source intersection	❌	4.4 years	4.4 years
#15	Fix example of non-similar CSP sources with different ports	❌	4.4 years	4.4 years
#16	Meaning of 'self' in csp attribute	❌	4.4 years	4.4 years
#17	Rewrite source expression intersection without using similarity	❌	4.4 years	4.4 years
#21	Limit length of CSP attribute	❌	3.3 years	3.3 years
#24	Editor's draft not getting autoupdated	❌	2.6 years	2.6 years
#27	Broken references in Content Security Policy: Embedded Enforcement	❌	2.1 years	2.1 years
#30	Redirect https://w3c.github.io/webappsec-csp/embedded/	❌	1.8 weeks	6 days