chore(deps): clear 9 high-severity npm-audit advisories - #4
Merged
Conversation
Stub anchor for clearing the 9 high-severity npm-audit advisories in the dependency tree (postcss, the vitest/coverage chain, and the eslint/ minimatch/brace-expansion chain). Work follows. Refs #1843 Co-Authored-By: Claude <noreply@anthropic.com>
Resolve the 9 high-severity npm audit findings (superproject #1843): postcss (npm audit fix), the vitest/coverage-v8/test-exclude/glob chain (bump to vitest 4.1.10), and the eslint/@eslint/config-array/eslintrc/ minimatch/brace-expansion chain via a targeted `minimatch` override (avoids the breaking eslint 10 bump npm suggests). The vitest 4 bump changed the v8 coverage provider's branch-detection accuracy (AST-aware remapping replaces the old v8-to-istanbul mapping), surfacing real, previously-masked branch-coverage gaps in locales.ts, I18nProvider.tsx, and version.ts. Added tests for detectBrowserLocale, initialLocale, persistLocale, the 4-letter script-subtag path, and the no-`initial`-prop I18nProvider path to close those gaps with real coverage rather than lowering the threshold. tsconfig.app.json also needed "node" added to `types` — vitest 4 no longer leaks ambient @types/node into the app program the way vitest 3 did, and build-scripts.test.ts uses Buffer. npm audit: 0 vulnerabilities (was 9 high). Co-Authored-By: Claude <noreply@anthropic.com>
MichaelTaylor3d
marked this pull request as ready for review
July 31, 2026 04:23
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.
What
Clears the 9 high-severity npm-audit advisories in the dependency tree (
#1843) — all pre-existing transitive/dev-tooling deps, surfaced while shipping #1842. Dependency-hygiene only; no app-feature/behavior change.Advisory breakdown
postcss— path traversal; non-breaking fix.@vitest/coverage-v8,glob,test-exclude) — bumpvitest+@vitest/coverage-v8 → ^4.eslint,@eslint/config-array,@eslint/eslintrc,minimatch,brace-expansion) — cleared via a targetedoverrides: { minimatch: ^10 }(routes onto patchedbrace-expansion 5.0.9) rather than a breakingeslint@10bump. Same pattern proven in bugreport.dig.net#16.Verification (before ready-for-review)
npm audit→ 0 (or documented no-fix remainder)Closes #1843
🤖 Generated with Claude Code
Generated by Claude Code