The warning happens because the regex contains a "." character, which allows arbitrary unicode characters and could in some circumstances lead to security issues. Unfortunately this pattern is trying to match filenames, which indeed could have arbitrary unicode characters. We can easily suppress this warning by adding "regexp: true" to the /*jslint*/ line at the top of the file. Is this an acceptable fix? I'll be happy to submit a new pull request with that change if you think it's the right thing to do.

BTW the automatic build that happens when I submit a pull request doesn't give this jslint error; I guess the auto-builder has that warning disabled.