Repository navigation
Conversation
Automated dependency upgrade by OrbisAI Security
| "engines": { | ||
| "node": ">= 0.10" | ||
| }, | ||
| "funding": { |
Owner
There was a problem hiding this comment.
Why is this funding field here?
Author
There was a problem hiding this comment.
The funding block is registry metadata for proxy-addr@2.0.8; 2.0.7 didn't have it, and npm adds it to the lockfile automatically. The diff is otherwise limited to the version, resolved URL and integrity hash for that one package. I checked that npm ci resolves proxy-addr@2.0.8 (via express 4.22.1), and that GHSA-jqcg-44mw-7w3h / CVE-2026-90711 lists 2.0.8 as the first patched version. I haven't established that the vulnerable path is reachable here, so this is a dependency fix, not a confirmed exploit.
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.
This upgrades
proxy-addr(currently 2.0.7) to 2.0.8, which carries the fix for CVE-2026-90711. The package is present in this repository's dependency tree; I have not verified that your code reaches the affected function.Reference: CVE-2026-90711
What changed
package-lock.jsonVerification
No automated check could be run against this repository, so this change is unverified beyond review. Please treat it as a suggestion.
Automated security fix by OrbisAI Security