chore: fix npm audit vulnerabilities#6
Merged
Merged
Conversation
ebd501b to
242ce5f
Compare
242ce5f to
41f2d70
Compare
nmccready
approved these changes
Mar 2, 2026
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.
npm audit fix
Ran
npm audit fixto address dependency vulnerabilities.Changes
package-lock.json(nopackage.jsonchanges)--forcewas not used (it would downgradetypescript-eslintto 8.14.0 as a breaking change but still wouldn't resolve the remaining issues)Audit Summary
Unresolved Vulnerabilities
All 9 remaining moderate vulnerabilities stem from ajv <8.18.0 (GHSA-2g4f-4pwh-qvx6 - ReDoS with
$dataoption). These are deep transitive dependencies ofeslint→@eslint/eslintrc→ajv. No fix is available vianpm audit fix— resolution requires eslint to update its ajv dependency upstream.Tests
All 35 tests passing ✅