fix(security): pin root devDependencies to exact versions#67
Open
xiaolai wants to merge 1 commit intocodeaholicguy:mainfrom
Open
fix(security): pin root devDependencies to exact versions#67xiaolai wants to merge 1 commit intocodeaholicguy:mainfrom
xiaolai wants to merge 1 commit intocodeaholicguy:mainfrom
Conversation
Co-Authored-By: Claude Code <noreply@anthropic.com>
This was referenced Apr 21, 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.
Bug
The root
package.jsondeclares devDependencies with^(caret) ranges:The
^operator allows npm to silently install any compatible minor or patch version. If any of these packages (or their dependencies) is compromised at a minor/patch release,npm installon a fresh checkout without a lock file would pull in the malicious version.Fix
Pins each devDependency to the exact version currently resolved in
package-lock.json:@nx/js^22.4.022.6.5husky^9.1.79.1.7nx^22.4.022.6.5These are the versions already locked in
package-lock.json, so no behavior changes for developers usingnpm ci. This only affects freshnpm installruns in environments without the lock file.Impact
Low severity. Supply chain hardening — eliminates a window where a compromised minor/patch release could be silently installed in CI or contributor environments that don't use
npm ci.