Skip to content

🔧 deps(mastra): fix js-yaml DoS alert (#36)#353

Merged
Chisanan232 merged 1 commit into
mainfrom
fix/dependabot-js-yaml
Jul 21, 2026
Merged

🔧 deps(mastra): fix js-yaml DoS alert (#36)#353
Chisanan232 merged 1 commit into
mainfrom
fix/dependabot-js-yaml

Conversation

@Chisanan232

Copy link
Copy Markdown
Contributor

Summary

  • Fixes Dependabot alert [AAASM-2311] ✅ (verify): Verify AAASM-2196 policy enforcement and approval scenarios acceptance criteria #36: js-yaml YAML merge-key chains can force quadratic CPU consumption (DoS), vulnerable range >=4.0.0,<4.3.0, patched at 4.3.0.
  • js-yaml is a transitive dependency in node/mastra (pulled in via gray-matter), already pinned through an existing pnpm.overrides entry at 4.2.0. Bumped that override to ^4.3.0.
  • Regenerated node/mastra/pnpm-lock.yaml via pnpm install; confirmed no js-yaml version in the vulnerable range remains in the lockfile.
  • No direct dependency change, no other package versions touched.

Why

Resolve the open Dependabot security alert without expanding js-yaml to a direct dependency, per repo policy.

Test plan

  • pnpm install in node/mastra regenerates lockfile cleanly (only js-yaml bumped to 4.3.0, plus incidental libc metadata churn from pnpm's resolver)
  • pnpm run build (tsc --noEmit) passes
  • pnpm test (vitest) — 2 test files, 7 tests, all passing
  • Confirmed grep js-yaml node/mastra/pnpm-lock.yaml shows only 4.3.0

Closes alert: https://github.com/ai-agent-assembly/examples/security/dependabot/36

Bumps the existing pnpm.overrides pin for the transitive js-yaml
dependency from 4.2.0 to ^4.3.0, resolving Dependabot alert #36
(YAML merge-key chains can force quadratic CPU consumption / DoS).
@sonarqubecloud

Copy link
Copy Markdown

@Chisanan232
Chisanan232 merged commit a078144 into main Jul 21, 2026
16 checks passed
@Chisanan232
Chisanan232 deleted the fix/dependabot-js-yaml branch July 21, 2026 08:51
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.

1 participant