Conversation
Remove caret range (^1.10.0 → 1.10.0) to ensure npm/pnpm never resolves a compromised version on fresh install or update. Context: axios@1.14.1 and axios@0.30.4 were compromised via the plain-crypto-js malware package.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Sync lockfile specifier (^1.10.0 → 1.10.0) so npm ci doesn't fail on the mismatch.
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
1 participant
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.
Summary
^1.10.0→1.10.0) to prevent resolving a compromised axios version on fresh install or updateplain-crypto-jsmalware package (ref)Test plan
npm cistill works (lockfile already pins 1.10.0)Note
Low Risk
Low risk dependency metadata change; it only restricts version resolution and shouldn’t affect runtime behavior beyond preventing accidental upgrades.
Overview
Pins
axiosinpackage.jsonfrom^1.10.0to the exact1.10.0to prevent fresh installs/updates from resolving to newer (potentially compromised) versions.Written by Cursor Bugbot for commit 8db6773. Configure here.