Repository navigation
fix: patch vulnerable ScopeGuard dependencies - #12
Merged
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
2 participants
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.
The locked dependency tree contained three security advisories affecting nanoid, yaml, and Vitest/@vitest/mocker. This patch updates only the reviewed package set and raises the yaml and Vitest minimum versions; application rules, source code, CI configuration, and version 0.2.0 are unchanged.
Adds concise project planning, work queue, and change documentation. The project plan correctly identifies the repository as public.
Validation: independent review reproduced a fresh npm 10 installation on Node 22, zero vulnerabilities in full and omit-dev audits, typecheck, 20 passing tests, and build. Local worker smoke passed 200/404/405 cases. GitHub CI will validate this PR. Deployment is outside this change.