security: bump 19 package(s) in npm#5
Open
vtiwari-story wants to merge 1 commit into
Open
Conversation
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.
Security dependency upgrade
This PR was opened by depagent to address 19 security alert(s) in the
npmecosystem.Each package is pinned to exactly the patched version reported by Dependabot's
first_patched_version— not a range. To restore a range constraint (e.g.^x.y.z), edit the manifest after merge.Alerts addressed
nextnextnextnextnextnextnextnextnextnextnextnextnextnextnextnextnextnextnextNotes
pnpm.overrides/overrides/resolutions). The vulnerable package isn't declared directly in the manifest — the override pins it to the patched version across the entire dependency graph for that workspace.npm error code EOVERRIDE
npm error Override for next@15.5.10 conflicts with direct dependency
npm error A complete log of this run can be found in: /Users/securient/.npm/_logs/2026-05-20T17_47_31_735Z-debug-0.log. Please run your package manager's install locally and commit the lockfile update.
Generated by depagent —
storyprotocol/react-quickstart.