fix(deps): resolve npm audit advisories and sync lockfile#5
Merged
Conversation
Sync package-lock.json engines with package.json (>=22.12.0); it was left stale when engines was bumped without re-running npm install. Run npm audit fix for the in-range vite advisory. Add overrides forward-patching dev-only transitive advisories: esbuild ^0.28.1, undici ^7.28.0, tmp ^0.2.7. Takes npm audit from 9 vulnerabilities to 2. The remaining two (moderate, js-yaml via gray-matter) have no gray-matter-compatible fix and are low real-risk (trusted frontmatter input only). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Summary
Resolves npm audit advisories and fixes a package-lock drift.
Result: npm audit 9 to 2 vulnerabilities. Build + 28 tests pass on the bumped versions (tsup, vitest, and the bintastic test harness all verified).
Remaining (accepted)
2 moderate: js-yaml via gray-matter — the only consumer-facing advisory. No gray-matter-compatible fix (gray-matter 4 pins js-yaml 3.x; forcing js-yaml 4.x breaks gray-matter frontmatter parsing, verified). Low real risk: a quadratic DoS in YAML merge-key handling, and pluginpack only parses frontmatter from the repo's own trusted source plugins. The genuine fix is upstream.
🤖 Generated with Claude Code