[typeagent-bot]

Automated Dependabot Alert Remediation

This PR was automatically generated by the fix-dependabot-alerts workflow.
Each fix was applied individually and build-verified before inclusion.

Summary

• Applied (2): serialize-javascript vite
• **Blocked (1):**js-yaml
• **No patch available (2):**deepmerge, extract-zip
• Deferred (0): (none)
• Rolled back (6): body-parser underscore undici uuid xml2js zod
• Skipped (recent rollback, 14): brace-expansion @azure/msal-node @hono/node-server @modelcontextprotocol/sdk @vue/server-renderer brace-expansion diff electron esbuild hono katex nodemailer prosemirror-view qs
• Workspaces with analysis failures: (none)
• Build: Passed
• Shell packaging: passed

The analysis also audits the lockfile directly. Its results can differ from the GitHub Dependabot REST API.

Why blocked packages could not be auto-fixed

Dependency chains

===== docs =====

══════════════════════════════════════════════════════════════════════
  Reading cached Dependabot alerts
══════════════════════════════════════════════════════════════════════
  Snapshot: /tmp/dependabot-alerts.json (89 alert(s))
  Found 10 alert(s) across 2 package(s)

══════════════════════════════════════════════════════════════════════
  Analyzing vulnerabilities
══════════════════════════════════════════════════════════════════════

  [1/2] 📦 brace-expansion (high) — ✗ 5.0.5 → need ≥5.0.12
     Fix: pnpm update brace-expansion -r
     → minimatch@10.2.4
       → maximatch@0.1.0
         → @11ty/recursive-copy@4.0.3
           … 1 more level(s) collapsed (use --show-chains=full)
  ⚠  Could not resolve shell production deps — shell packaging post-check will still validate

  [2/2] 📦 js-yaml (high) — ✗ 3.14.2, ✗ 4.1.1 → need ≥4.3.2
     ↳ used by: typeagent-docs
     Actions: (requires --auto-fix)
       [override] gray-matter@4.0.3 pins js-yaml ^3.13.1, already at latest — no update available
     Risk: ▲ high — major version bump 3.14.2 → 4.3.2, 1 parent(s) may break
     → @11ty/eleventy@3.1.2
       → typeagent-docs
     → gray-matter@4.0.3
       → @11ty/eleventy@3.1.2 (see above)

══════════════════════════════════════════════════════════════════════
  Resolution plan (dry run)
══════════════════════════════════════════════════════════════════════
  ✓  [dry-run] pnpm update brace-expansion -r → >=5.0.12

══════════════════════════════════════════════════════════════════════
  Summary
══════════════════════════════════════════════════════════════════════

  1 to resolve | 1 blocked

  Fixed packages:
     ✓  [update] brace-expansion 5.0.5 → >=5.0.12

  Risk assessment:
     ▲ high  [override] js-yaml >=4.3.2: major version bump 3.14.2 → 4.3.2, 1 parent(s) may break

  Run with --auto-fix to fix: js-yaml
    (or --apply-overrides for: js-yaml)

  ⚠  DRY RUN — no changes were made. Run without --dry-run to apply.

How this works

1. Analyses open Dependabot alerts and the lockfile
2. Applies each fix individually with build verification
3. Rolls back fixes that break the build
4. Includes only verified fixes

Review checklist

• Check for breaking changes
• Investigate rolled-back packages
• Run relevant tests