You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mixed npm and pnpm locks report an upgrade as applied without changing either lock #1691
The accompanying fixture contains a package.json with express-rate-limit@8.6.1, which depends on ip-address through ^10.2.0. Its npm-generated lock resolves ip-address@10.5.1 and its pnpm-generated lock resolves ip-address@10.4.0. The files were generated with the respective package managers using historical release cutoffs; neither lock was edited by hand.
With Socket CLI authenticated by the normal supported method, from a fresh copy of the fixture:
The targeted apply exits 1, so continue to the diff and rescan even when using a shell configured to exit on errors.
Observed
The initial plan proposes upgrading both locked versions to 10.7.4 for each of the three GHSAs. The apply result is ok: false and reports No file was changed for this upgrade for the 10.5.1 target under all three GHSAs. It also reports the 10.4.0 targets as applied and lists package-lock.json in modifiedFiles.
However, git diff is empty: the npm lock still resolves 10.5.1 and the pnpm lock still resolves 10.4.0. A fresh dry-run still proposes both versions. Thus the reported applied target and modified-file list do not match the actual fixture diff.
For comparison, separate fixtures with the same manifest and only the npm lock or only the pnpm lock both apply the three targeted upgrades successfully, changing the corresponding lock to 10.7.4; the targeted GHSAs are absent from each fresh rescan.
Expected
Each supported lockfile should either be upgraded and reported accurately, or the result should identify the unsupported mixed-lock condition without reporting unchanged files or unresolved targets as applied.
Activity