w3c/webappsec-subresource-integrity Issues

Last updated Nov 8, 2025, 5:58:15 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.

13 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
#57	Applying SRI to HTTP ranges	❌	9.1 years	9.1 years
#107	Only recommending collision resistance	❌	4.2 years	4.1 years
#116	Define equality comparator for metadata	❌	3.5 years	3.5 years
#121	base64-related requirements are broken	❌	2.6 years	2.5 years
#124	Normative references to discontinued specs in Subresource Integrity	❌	1.2 years	1.2 years
#154	current bytesMatch algorithm ineffective and in worst case scenario sec. vuln.	❌	2.7 months	2.5 months
#156	Integrity-Policy gaps for WAICT	❌	1.4 weeks	3 days
#159	WAICT enforcement modes	❌	1.4 weeks	3 days
#160	Inline Manifest	❌	1.4 weeks	3 days
#161	Multiple Manifests	❌	1.4 weeks	3 days
#163	Support for multiple resources per Hash (Multiple resources in a JS file)	❌	1.4 weeks	2 days
#164	Proposed covered resource types	❌	1.4 weeks	2 days
#165	Integrity for source maps	❌	1.3 weeks	2 days