Bump path-to-regexp from 0.1.12 to 0.1.13#1067
Conversation
Bumps [path-to-regexp](https://github.com/pillarjs/path-to-regexp) from 0.1.12 to 0.1.13. - [Release notes](https://github.com/pillarjs/path-to-regexp/releases) - [Changelog](https://github.com/pillarjs/path-to-regexp/blob/v.0.1.13/History.md) - [Commits](pillarjs/path-to-regexp@v0.1.12...v.0.1.13) --- updated-dependencies: - dependency-name: path-to-regexp dependency-version: 0.1.13 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Slinky Test ReportLast Run: 2026-03-28 03:55:19 CST (Duration: 1m2.44s)
Failures by URL
|
There was a problem hiding this comment.
LGTM — security patch bumping path-to-regexp to fix CVE-2026-4867, only touching package-lock.json.
Extended reasoning...
Overview
This PR updates the path-to-regexp dependency (used as a transitive dependency of express) from 0.1.12 to 0.1.13 in package-lock.json. It is a single-file, lock-file-only change generated by Dependabot.
Security risks
The change specifically fixes CVE-2026-4867, which is a security vulnerability in path-to-regexp. Applying this patch reduces security risk rather than introducing it. The diff is a straightforward version/hash bump with no logic changes.
Level of scrutiny
This is a minimal, mechanical security patch to a lock file. The scope is extremely narrow — one dependency, one file, patch-level version bump. No application logic or configuration is affected.
Other factors
No bugs were found by the automated bug hunting system. No prior reviews exist on this PR. This is a standard Dependabot security update that is safe to auto-approve.
Bumps path-to-regexp from 0.1.12 to 0.1.13.
Release notes
Sourced from path-to-regexp's releases.
Changelog
Sourced from path-to-regexp's changelog.
Commits
9fd0c870.1.13 (#425)7ccf02cfix: CVE-2026-4867Maintainer changes
This version was pushed to npm by ulisesgascon, a new releaser for path-to-regexp since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.