fix critical vulnerabilities and remove unmaintaned dependency - #72
Merged
anttiviljami merged 2 commits intoFeb 18, 2026
Merged
Conversation
smolnikov
force-pushed
the
fix-critical-vulnerabilities
branch
from
November 25, 2025 10:41
df51c3c to
46ba398
Compare
Contributor
Author
|
@anttiviljami could you share your opinion on this? |
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 PR:
koa-proxywhich didn't have updates for 6 years now and introduces critical security vulnerabilities; replaces it with custom-made axios-based implementation of proxynpm auditpackage.json(to>=18as many dependencies inpackage-lock.jsonalready have it set, so current version doesn't truly support node 16) as this will require major version updateHow it was tested:
npm run build && npm run test