fix: npm package vulnerabilities - #69
Open
alronova wants to merge 1 commit into
Open
Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
illume
requested changes
Apr 14, 2026
illume
left a comment
Collaborator
There was a problem hiding this comment.
Thanks, can you please see if this is still needed?
Signed-off-by: alronova <aditya.divyam001@gmail.com>
alronova
force-pushed
the
fix/pkg-vulnerabilities
branch
from
April 15, 2026 06:00
7359771 to
0f0e0ad
Compare
Author
Yes, this fix was indeed needed. I checked for the security vulnerabilities again on the latest codebase from |
Author
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.
Fix
npmPackages VulnerabilitiesFixed 23 vulnerabilities (8 low, 4 moderate, 11 high severity) using
npm audit fix.Added 1 package, removed 1 package, changed 73 packages, and audited 1297 packages.
Changes Made
Vulnerabilities Before
Vulnerabilities After
Note
The low severity package vulnerabilities can also be fixed but they will introduce breaking changes to the project. Considering that, I ignored those vulnerabilities.
Testing done
npminstall completes with only 7 low severity vulnerabilities warningnpmaudit shows only low-severity issues remainI have signed-off my commits and rebased my branch with the latest commit on
main.@ashu8912 kindly review this PR whenever you get time.