Repository navigation
fix: remove vulnerable dependency versions identified by security audits - #17
Merged
Merged
Conversation
dphi
marked this pull request as ready for review
October 23, 2026 14:06
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.
Apply targeted dependency patches identified by fresh lockfile audits, retaining application behavior and the existing test/lint toolchain. Regenerate lockfiles using the package manager rather than editing integrity metadata.
Validation: the repaired dependency snapshot passed its package audit or OSV scan. Repository CI is being checked against the real application sources before merging. No advisories are suppressed.