Bump js-yaml from 4.1.0 to 4.1.1 in /components/frontend

[dependabot]

Bumps js-yaml from 4.1.0 to 4.1.1.

Changelog

Sourced from js-yaml's changelog.

[4.1.1] - 2025-11-12

Security

• Fix prototype pollution issue in yaml merge (<<) operator.

Commits

• cc482e7 4.1.1 released
• 50968b8 dist rebuild
• d092d86 lint fix
• 383665f fix prototype pollution in merge (<<)
• 0d3ca7a README.md: HTTP => HTTPS (#678)
• 49baadd doc: 'empty' style option for !!null
• ba3460e Fix demo link (#618)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

Claude Code Review

Summary

This PR updates the js-yaml dependency from version 4.1.0 to 4.1.1 to address a critical security vulnerability - a prototype pollution issue in the YAML merge (<<) operator. This is a dependabot-generated security patch that should be merged promptly.

The update is minimal, only affecting package-lock.json with the version bump and some additional nested dependencies for the @tailwindcss/oxide-wasm32-wasi package (unrelated to the security fix).

Recommendation: ✅ APPROVE AND MERGE

---

Issues by Severity

🟢 No Issues Found

This is a clean security patch with no code quality, security, performance, or architectural concerns.

---

Positive Highlights

✅ Security-Critical Update: Fixes CVE-level prototype pollution vulnerability in js-yaml
✅ Automated Dependency Management: Dependabot working as intended to keep dependencies secure
✅ Minimal Change Surface: Only lockfile changes, no source code modifications required
✅ Transitive Dependency: js-yaml is pulled in by @eslint/eslintrc (dev dependency), so the vulnerability is limited to development environment
✅ CI Passing: Most checks are passing or in progress, no blocking failures detected

---

Recommendations

Immediate Actions

1. ✅ Merge this PR immediately - Security patches should not wait, especially for prototype pollution which can lead to remote code execution in certain contexts
2. ✅ Monitor CI completion - Wait for in-progress checks (frontend lint, E2E tests) to complete successfully before merging

Post-Merge

3. 📊 Review dependabot configuration - Consider enabling auto-merge for patch-level security updates to reduce response time
4. 🔍 Audit other dependencies - Run npm audit to check for other potential vulnerabilities

Context Notes

• Impact Scope: Limited to development environment only (devDependency via ESLint)
• Prototype Pollution: This class of vulnerability can allow attackers to inject properties into Object.prototype, potentially leading to DoS or RCE
• Upstream Fix: The js-yaml maintainers addressed this in commit 383665f with proper prototype pollution prevention in the merge operator

---

Review completed by Claude Code Review
Automated review focusing on security, code quality, and best practices per CLAUDE.md guidelines

[dependabot]

Looks like js-yaml is up-to-date now, so this is no longer needed.