[DependOnMe] Bulk security fix - 3 issues#129
Open
dependonme-deriv wants to merge 2 commits into
Open
Conversation
Automatically regenerated by DependOnMe bot after package.json update. Branch: dependonme/bulk-fix-6efaf68a Package manager: npm
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Filespackage-lock.json
|
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.
Bulk Security Fix
This pull request was automatically generated by DependOnMe to fix 3 security issues at once.
Issues Fixed
Files Modified
package.jsonAI Summary
Fixed 3 security issues:
Fixes Applied:
[HIGH] esbuild — Missing binary integrity verification / RCE via NPM_CONFIG_REGISTRY
"esbuild": "^0.28.1"todevDependencies(direct dependency pin) and"esbuild": "^0.28.1"tooverrides(forces all transitive consumers to use safe version)esbuildis a transitive dependency pulled in byvite. Since upgradingvitealone may not guarantee a specificesbuildsub-version resolution, adding anoverridesentry ensures npm resolvesesbuildto>=0.28.1across the entire dependency tree.[LOW] esbuild — Arbitrary file read on Windows dev server
esbuildpinned to^0.28.1covers both HIGH and LOW advisories since both require>= 0.28.1.[MEDIUM] picomatch — Method Injection in POSIX Character Classes (CVE-2026-33672)
picomatchwas already at4.0.4in bothdevDependenciesandoverridesin the providedpackage.json. No change was needed in the manifest — thepackage-lock.jsonissue will be resolved upon runningnpm installwith the existing pinned version. The override and direct dependency entries remain at4.0.4to enforce the safe version across the dependency tree.What Was Changed:
devDependencies.esbuild"^0.28.1"overrides.esbuild"^0.28.1"devDependencies.picomatch"4.0.4""4.0.4"(unchanged — already correct)overrides.picomatch"4.0.4""4.0.4"(unchanged — already correct)^0.28.1— Low Risk: This is a patch/minor bump within the same major version.esbuildis a build tool (not a runtime dependency), so no application code is affected. Vite 7.x is compatible with esbuild 0.28.x. The^range allows future patch updates within 0.x.4.0.4— No Risk: Already at the required version in the manifest; this is purely a lock file regeneration concern.🧪 Testing Checklist:
npm installto regeneratepackage-lock.jsonwith the pinned versionsnpm ls esbuildshows0.28.1or higher for all instances in the treenpm ls picomatchshows4.0.4for all instances in the treenpm run buildto confirm the build succeeds with the new esbuild versionnpm run devto confirm the development server starts correctlynpm testto ensure all tests passtsc --noEmit)🔧 Manual Steps Required:
package.json, run:package.jsonand the regeneratedpackage-lock.jsonThis PR was created by DependOnMe - Automated Security Issue Management