Vulnerability Database · Pub · Package report
path_to_regexp: vulnerability history, versions and safety
path_to_regexp is a package in the Pub ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Pub ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on path_to_regexp 0.4.0 i
Updated on 23 Oct 2026
Good news: 0.4.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Unmaintained
- Popularity Not enough data
- Community Not enough data
What to do: Stay on 0.4.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.4.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 0.4.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Last release 67 months ago i
Version list, release dates, licence and dependants published by pub.dev, refreshed 23 Oct 2026. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Versions
Which versions are affected
Every version Vulert tracks for path_to_regexp, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- 0.4.0 06 Mar 2021
- 0.4.0-nullsafety.0 19 Dec 2020
- 0.3.0 13 Nov 2019
- 0.2.1 09 Mar 2019
- 0.2.0 31 Oct 2018
- 0.1.2 27 Jul 2018
- 0.1.1 04 Jul 2018
- 0.1.0 04 Jul 2018
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 0.4.0 | 06 Mar 2021 | none | — | — | Details → |
| 0.4.0-nullsafety.0 | 19 Dec 2020 | none | — | — | Details → |
| 0.3.0 | 13 Nov 2019 | none | — | — | Details → |
| 0.2.1 | 09 Mar 2019 | none | — | — | Details → |
| 0.2.0 | 31 Oct 2018 | none | — | — | Details → |
| 0.1.2 | 27 Jul 2018 | none | — | — | Details → |
| 0.1.1 | 04 Jul 2018 | none | — | — | Details → |
| 0.1.0 | 04 Jul 2018 | none | — | — | Details → |
All 8 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for path_to_regexp
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About path_to_regexp
Is path_to_regexp safe to use?
Vulert has no vulnerabilities on record for path_to_regexp in Pub at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is path_to_regexp's Vulert package health score?
Vulert scores path_to_regexp 67/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of path_to_regexp affected?
No. 0.4.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
How many vulnerabilities does path_to_regexp have?
0 vulnerabilities are recorded for path_to_regexp in the Pub ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new path_to_regexp vulnerabilities disclosed?
0 vulnerabilities were recorded for path_to_regexp in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of path_to_regexp are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor path_to_regexp for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the path_to_regexp version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.