fix remaining dependency audit issues - #11
Merged
Conversation
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.
What changed
Root cause
GitHub Dependabot showed no open alerts, but an independent Python audit found nine advisory records against Starlette 0.38.6, pulled transitively by the old FastAPI pin. The npm lockfile also lagged safe in-range releases despite having no known vulnerabilities.
Impact
The backend moves onto patched FastAPI/Starlette releases. Frontend direct dependency constraints remain unchanged; only safe in-range lockfile resolutions are refreshed.
Validation
pip-audit -r backend/requirements.txt— no known vulnerabilitiespip-audit -r requirements-dev.txt— no known vulnerabilitiesnpm audit --audit-level=low— zero vulnerabilitiesnpm ls --allnpm run buildnpm run test— 15 tests passed