Skip to content

security: upgrade vulnerable packages and document yarn resolutions#1061

Draft
MatiasArriola wants to merge 10 commits into
developmentfrom
security/sca-triage-fixes
Draft

security: upgrade vulnerable packages and document yarn resolutions#1061
MatiasArriola wants to merge 10 commits into
developmentfrom
security/sca-triage-fixes

Conversation

@MatiasArriola
Copy link
Copy Markdown
Contributor

Summary

  • Upgrade direct deps and add scoped yarn-berry resolutions for transitive vulnerabilities flagged by Dependency-Track (axios, flatted, handlebars, tar, picomatch per-parent, brace-expansion per-exact-parent, vite/rollup scoped to vite 4).
  • Add RESOLUTIONS.md documenting every entry in package.json resolutions with why / fixes / drop-when fields. Pre-existing pins whose rationale was recoverable from git history (@types/react, qs, diff, i18next) are now documented; one (@dhis2/ui-icons) remains in a "rationale not recovered" subsection.
  • Gitignore .claude/ (skill distributed externally) and the regenerable sca-triage-report.md.

Test plan

  • yarn install clean
  • yarn npm audit --severity high shows no remaining high-severity findings for the pinned packages
  • yarn why <pkg> confirms each new resolution actually fires (especially the versioned-parent brace-expansion pins, which decay silently)
  • App builds and starts (yarn start)
  • Re-run Dependency-Track workflow against this branch and verify no new high-severity findings

idelcano and others added 4 commits April 23, 2026 15:36
- Upgrade direct deps (axios, etc.) and add scoped yarn resolutions for
  transitive vulnerabilities (flatted, handlebars, tar, picomatch,
  brace-expansion, vite/rollup) flagged by Dependency-Track.
- Add RESOLUTIONS.md documenting every entry in package.json resolutions
  with why / fixes / drop-when fields, including pre-existing pins whose
  rationale was recoverable from git history.
- Gitignore .claude/ (skill distributed externally) and the regenerable
  sca-triage-report.md.
@MatiasArriola MatiasArriola changed the base branch from feature/test_githubaction to development May 8, 2026 15:14
@MatiasArriola MatiasArriola reopened this May 8, 2026
@bundlemon
Copy link
Copy Markdown

bundlemon Bot commented May 8, 2026

BundleMon

No change in files bundle size

Groups updated (1)
Status Path Size Limits
Build Folder
./**/*
2.67MB (-90.56KB -3.21%) +20%

Final result: ✅

View report in BundleMon website ➡️


Current branch size history | Target branch size history

BOM analysis after the previous commit showed picomatch@4.0.3 still in
the tree under vite@7.3.2 and vitest@3.2.4 — neither covered by the
existing @rollup/pluginutils and tinyglobby parent paths. Adding
vite/picomatch and vitest/picomatch resolutions at ^4.0.4 closes
GHSA-c2c7-rcm5-vvqj for those subtrees.
- lodash 4.17.23 -> 4.18.1 + resolution to flush transitive 4.17.21
  (clears CVE-2026-4800 critical, CVE-2021-23337 high)
- minimatch per-parent pins resolve dev-tool tree to 3.1.5/7.4.9/9.0.9
  (clears CVE-2026-26996/-27903/-27904 high)
…scripts

fix: add "nsSeparator: false" to all i18n calls that contained warnings due to ":" usage
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants