fix-deps-js-yaml-432

YA
1mo ago
+18-28

User description

Kills open HIGH js-yaml alerts (dev scope, transitive + direct): minimal pins with advisory-fixed identifiers (v4 ^4.3.2, v3 ^3.15.2 via per-parent reference overrides where both lines coexist), npm ls validates clean with no invalid flags. Manifest + lock only. Do-not-merge until CI green post-restore per standing law.

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Summary by Sourcery

Resolve high-severity js-yaml dependency alerts across direct and transitive development dependencies.

Bug Fixes:

  • Update js-yaml to advisory-fixed versions and enforce the secure version through dependency overrides.

Build:

  • Refresh the package lockfile to reflect the dependency updates.

[!NOTE]
Low Risk
Dev-only dependency and lockfile updates for a patched YAML parser; no runtime or API surface changes in this repo.

Overview
Addresses HIGH security advisories on js-yaml in this package’s dev toolchain by bumping the direct devDependency from 4.1.0 to ^4.3.2 and adding an overrides entry so transitive installs (e.g. under @redocly/openapi-core) resolve to the same fixed line instead of older nested copies.

package-lock.json is regenerated accordingly: the hoisted js-yaml@4.3.2 replaces 4.1.0, and the separate 4.3.1 nested under Redocly is dropped in favor of the overridden version. No OpenAPI spec or script source changes—only manifest and lockfile.

Reviewed by Cursor Bugbot for commit 6c33115d65b67a7979cd491020453a4e29b90c67. Bugbot is set up for automated code reviews on this repo. Configure here.

CodeAnt-AI Description

Update js-yaml to a security-fixed version across development tooling

What Changed

  • Replaces js-yaml 4.1.0 with version 4.3.2
  • Ensures tools that depend on js-yaml use the updated version instead of retaining an older nested copy
  • Removes the previously locked js-yaml 4.3.1 installation

Impact

✅ Removes known high-severity js-yaml alerts
✅ Keeps OpenAPI linting and generation dependencies on a fixed release
✅ Avoids older nested js-yaml copies

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.