Repository navigation
Conversation
Refresh the lockfile so @azure/identity resolves to 4.14.1, which allows @azure/msal-node ^7.1.0. Fixes GHSA-xcx6-jx8p-x3h5. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: Nithya Subramanian <nithyasu@microsoft.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
nicolejms
approved these changes
Nov 4, 2026
nicolejms
left a comment
There was a problem hiding this comment.
Approved with one non-blocking comment on the unrelated integrity hash changes.
| "node_modules/jsonwebtoken": { | ||
| "version": "9.0.3", | ||
| "integrity": "sha512-MT/xP0CrubFRNLNKvxJ2BYfy53Zkm++5bX9dtuPbqAeQpTVe0MQTFhao8+Cp//EmJp244xt6Drw/GVEGCUj40g==", | ||
| "integrity": "sha1-bNV6sB6bCsB8uEfVPTybbuMfeuI=", |
There was a problem hiding this comment.
Non-blocking: Please restore the original SHA-512 integrity values for the 13 packages whose versions did not change. This update also replaces those hashes with SHA-1, which reduces collision resistance and is not needed for the MSAL fix. Keep the three intended package version updates.
nithyatsu
enabled auto-merge (squash)
November 4, 2026 18:12
kachawla
approved these changes
Nov 4, 2026
willdavsmith
approved these changes
Nov 4, 2026
lakshmimsft
approved these changes
Nov 4, 2026
willtsai
approved these changes
Nov 4, 2026
This branch has not been deployed
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.
Summary
Refresh
samples/demo/package-lock.jsonso@azure/identityresolves to 4.14.1, which pulls in@azure/msal-node7.1.2. This fixes Dependabot alert #426 (GHSA-xcx6-jx8p-x3h5).Reason for change
Dependabot couldn't fix this alert on its own.
@azure/monitor-opentelemetrydepends on@azure/identity, and every identity release before 4.14.1 capped msal-node below 7. The fix is 7.1.0. identity 4.14.1 came out on Oct 29 and allows^7.1.0, and monitor-opentelemetry already accepts it, so a lockfile refresh is enough. No package.json change and no override.The other rows in #2722 came from the old v0.61 default branch. The body-parser auth failure was the private registry URLs that #2719 removed, and those alerts are already fixed.
Part of #2722
How to test
samples/demo, runnpm update @azure/identity --package-lock-only. Expected: only@azure/identity(4.14.0 to 4.14.1),@azure/msal-node(6.0.1 to 7.1.2), and the nested@azure/msal-common(16.14.1 to 16.15.0) change.grep -c '"resolved"' samples/demo/package-lock.json. Expected:0.samples/demoimage withnpm cion node 22. msal-node 7 needs node 20 or later.File change summary
samples/demo/package-lock.json@azure/identityto 4.14.1,@azure/msal-nodeto 7.1.2, and the nested@azure/msal-commonto 16.15.0.