Repository navigation
fix: npm audit fix gegen High-Severity in js-yaml - #333
Merged
Merged
Conversation
CI Security-Audit-Job schlug auf testing fehl (js-yaml CPU-DoS via maxTotalMergeKeys, transitiv über eslint/@eslint/eslintrc). Nur devDependency-seitig betroffen. npm audit fix (ohne --force) behebt es ohne Breaking Change; verbleibend 16 moderate Findings (bekannt, dokumentiert in CLAUDE.md). Verifiziert: npm audit --audit-level=high exit 0, tsc --noEmit clean, lint clean, 453 Tests grün, Web-Build erfolgreich. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
🔀 Mergeability-Report✅ Konfliktfrei mergebar ( CI-Checks: ✅ keine fehlgeschlagenen Checks ⏳ ⚙️ Workflow Linting / actionlint Merge-Checkliste
Kostenlos generiert von reusable-mergeability.yml · keine API-Kosten · review-gate: |
This was referenced Sep 20, 2026
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
1 participant
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.
Problem
CI-Job "Security Audit" schlug auf
testingfehl (PR #331, Run 35110374165): neue high-severity Lücke injs-yaml(CPU-DoS viamaxTotalMergeKeys, GHSA-2883-xcg3-v3hh), transitiv übereslint/@eslint/eslintrc— reine devDependency, nicht im Laufzeit-Bundle.Fix
npm audit fix(ohne--force) — kein Breaking Change laut npm. Nurpackage-lock.jsonbetroffen.Verifiziert
npm audit --audit-level=high→ exit 0 (16 moderate verbleibend, bekannt/dokumentiert)npx tsc --noEmit→ cleannpm run lint→ cleannpm run test:ci→ 453/453 Tests grün, Coverage über Schwellenwertennpm run build:web→ erfolgreich🤖 Generated with Claude Code