petri/logview: pin react-router-dom to 7.15.0 (CVE fixes) + add min-release-age#3682
Open
benhillis wants to merge 2 commits into
Open
petri/logview: pin react-router-dom to 7.15.0 (CVE fixes) + add min-release-age#3682benhillis wants to merge 2 commits into
benhillis wants to merge 2 commits into
Conversation
Resolves CVE-2026-42211, CVE-2026-42342, and CVE-2026-40181 in react-router/react-router-dom. The lockfile now resolves to 7.17.0. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the petri/logview single-page React app’s routing dependency to pick up upstream security fixes and clear Component Governance alerts.
Changes:
- Bumped
react-router-domdependency from^7.12.0to^7.15.0. - Updated
package-lock.jsonto the resolved versions (react-router-dom/react-routerat7.17.0) consistent with the new semver range.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
petri/logview/package.json |
Updates the declared react-router-dom version range to ^7.15.0. |
petri/logview/package-lock.json |
Refreshes the lockfile to the new resolved react-router-dom/react-router versions and associated metadata. |
Files not reviewed (1)
- petri/logview/package-lock.json: Language not supported
Member
|
As a general policy, we should not take such new releases (7.17 is currently just 2 days old), especially from the npm ecosystem, to avoid undetected supply chain attacks. We should enforce this via |
Pin react-router-dom to the oldest release (7.15.0) that fixes all three flagged advisories (CVE-2026-42211, CVE-2026-42342, CVE-2026-40181) rather than floating to the latest, and add an .npmrc with min-release-age=7 to refuse npm releases newer than 7 days, reducing exposure to undetected supply-chain attacks. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
benhillis
changed the title
jstarks
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pins
react-router-dominpetri/logviewto the oldest release that fixes all flagged Component Governance advisories, and adds an.npmrcsupply-chain guard.Dependency fix
Pins
react-router-domto exactly7.15.0(lockfile resolvesreact-router/react-router-domto7.15.0).7.15.0is the oldest release that fixes all three flagged advisories:Previously the range was
^7.12.0/^7.15.0, which floated the lockfile to7.17.0(only a couple days old at the time). We now pin to the minimal fixed version rather than the latest, to avoid pulling in very new, undetected supply-chain attacks.logview is a client-side SPA (not Framework Mode), so real exposure was low, but this clears the CG alerts.
Supply-chain guard
Adds
petri/logview/.npmrcwithmin-release-age=7, which refuses to install any npm release published within the last 7 days (supported by npm >= 11.10.0). This reduces the window of exposure to undetected supply-chain attacks in the npm ecosystem.Validation
npm installreports 0 vulnerabilitiesnpm run build(vite) succeeds