Repository navigation
chore: automated npm audit fix - #45
Closed
ProduktEntdecker wants to merge 1 commit into
Closed
ProduktEntdecker wants to merge 1 commit into
ProduktEntdecker wants to merge 1 commit into
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueComment |
Owner
Author
|
Überholt durch den neueren automatischen npm-audit-Lauf #50. Orchestrator-Aufräumen 11.10.2026, bei Bedarf wieder öffnen. |
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
Automated weekly dependency hygiene check (2026-08-31). Ran
npm audit fix(no--force), which cleanly resolved 1 of 6 known vulnerabilities via a transitive lockfile-only bump.package.jsonis unchanged.Advisories fixed
Not auto-applied (needs manual review)
The remaining 5 advisories (esbuild moderate-DoS, vite, vite-node, @vitest/mocker, vitest — critical arbitrary file read) all only resolve via
npm audit fix --force, which would bumpvitestfrom2.1.9to4.1.11— a semver-major breaking change. Per policy,--force/breaking fixes are never auto-applied; this needs a deliberatevitestv4 migration in a follow-up PR.npm outdatedalso flagged (informational only, nothing auto-applied):Test plan
npm run build(tsc) passes cleanly after the fixpackage-lock.jsonchanged;package.jsonuntouchedGenerated by Claude Code