Thank you@stof, I didn't know that denial of service was actually a thing with regex. I updated accordingly.

@alexandre-daubois this can be a thing when you allow user input for the string being matched by the regex (which could totally happen in this component). Backtracking engines (like PCRE) have an exponential complexity based on the length of the input when attempting to match an affected regex (and failing to match it, as this is the worse case of backtracking).

This is commonly reported in the npm ecosystem (also because JS does not support possessive quantifiers in its Regexp syntax, and so cannot apply the easy fix to prevent them in many cases, making the issue more common)

Applied your suggestions, it makes the code a bit simpler. Thanks!

I reworked the whole PR to keep pushing forward the compliance test suite. This PR removes 265 skips, so that's pretty nice.

Status: Needs Review

@alexandre-daubois FYI in#60793 I had to skip three more tests

They are added back and fixed in this PR. Thanks!

Thank you@alexandre-daubois.