path-to-regexp

9.0.0 · 22 Oct 2026MIT310.6M / weekRepository Homepage npm Atom feed

Upgrading path-to-regexp From 0.1.10 to 0.1.11

Same major only

1 release in betweennotes for 0

Reading releases, release notes and advisories…

Other targets from 0.1.10Newest 0.x0.2.5 Clears its 2 advisories0.1.13 Latest9.0.0

0.1.10yours
0.1.11target

?
changes to make: 0
advisories fixed: ?
new: ?
fixes

Counted from 0 of 1 release notes. Advisories are counted from the advisory database, in full.

Security

2 advisories still affect 0.1.11

path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parametershigh · GHSA-37ch-88jc-xwx2
path-to-regexp contains a ReDoShigh · GHSA-rhx6-c78j-4q9w

Upgrading to 0.1.13 clears them.

Upgrade to 0.1.11

npm install path-to-regexp@0.1.11

What 0.1.11 needs

Reading 0.1.11's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 0.1.11. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
2 advisories still affect 0.1.11.