url-regex-safe
Advanced tools
Comparing version 1.0.0 to 1.0.1
{ | ||
"name": "url-regex-safe", | ||
"description": "Regular expression matching for URL's. Maintained, safe, and browser-friendly version of url-regex. Resolves CVE-2020-7661. Works in Node v10.12.0+ and browsers.", | ||
"version": "1.0.0", | ||
"version": "1.0.1", | ||
"author": "Nick Baugh <niftylettuce@gmail.com> (http://niftylettuce.com/)", | ||
@@ -6,0 +6,0 @@ "browser": { |
@@ -23,2 +23,3 @@ # url-regex-safe | ||
* [Quick tips and migration from url-regex](#quick-tips-and-migration-from-url-regex) | ||
* [Limitations](#limitations) | ||
* [Contributors](#contributors) | ||
@@ -132,2 +133,7 @@ * [License](#license) | ||
## Limitations | ||
Since we cannot use regular expression's "negative lookbehinds" functionality (due to [RE2][] limitations), we could not merge the logic from this [pull request](https://github.com/kevva/url-regex/pull/67/commits/6c31d81c35c3bb72c413c6e4af92a37b2689ead2). This would have allowed us to make it so `example.jpeg` would match only if it was `example.jp`, however if you pass `example.jpeg` right now it will extract `example.jp` from it (since `.jp` is a TLD). An alternative solution may exist, and we welcome community contributions regarding this issue. | ||
## Contributors | ||
@@ -134,0 +140,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
68646
172