Repository navigation
chore: automated npm audit fix - #44
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 run (
npm audit fix, no--force).Fixed (semver-compatible, no
package.jsonchange):nanoid: 3.3.16 -> 3.3.18 (fixes GHSA-2v37-7h3g-55p8, high severity — indefinite loop in custom generators when size is zero)Build:
npm run build(tsc) passed cleanly after the fix.Remaining vulnerabilities (NOT auto-fixed — require a major bump)
npm audit fix --forcewould upgradevitest2.1.9 -> 4.1.11 (semver-major, breaking) to resolve these. Left for manual review per policy (no automatic major bumps):vitest<=3.2.5 — critical — GHSA-5xrq-8626-4rwpvite<=6.4.2 — high — GHSA-4w7w-66w2-5vf9, GHSA-v6wh-96g9-6wx3, GHSA-fx2h-pf6j-xcffesbuild<=0.24.2 (viavite) — moderate — GHSA-67mh-4wv8-2f99@vitest/mocker<=3.0.0-beta.4 (viavite) — moderatevite-node<=2.2.0-beta.2 (viavite) — moderateAll five are dev-only (test tooling), transitively pulled in by
vitest. Upgradingvitestto 4.x is a breaking change and needs a dedicated PR with test-suite verification.Also outdated (informational only, not touched)
@types/nodetsxtypescriptvitestzodTest plan
npm cisucceedednpm audit fixapplied (no--force, no major bumps)package-lock.jsondiff — onlynanoidversion bumped, nopackage.jsonchangesnpm run buildpassedGenerated by Claude Code