Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.1.0 to 4.1.1. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.1.0...4.1.1) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.1.1 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
✓ Safe to upgradeI recommend merging this upgrade because js-yaml is only used as a dev dependency (likely for Cypress testing configuration) with no direct code imports found in the codebase. The upgrade patches a prototype pollution security vulnerability while maintaining full backward compatibility with no breaking changes. The security fix strengthens protection against proto key manipulation attacks. What we checked
Dependency Usage
Changesjs-yaml upgraded with a critical security fix that blocks prototype pollution attacks by preventing proto key manipulation in the YAML merge operator. The update strengthens object construction safeguards across both mergeObjects() and constructMapping() functions.
View 3 more changes
References (3)[1]: js-yaml declared as devDependency only (not production dependency), limiting exposure Line 81 in 69f30fc [2]: Upgrade from 4.1.0 to 4.1.1 - patch version with security fix for prototype pollution (GHSA-mh29-5h37-fv8m) Line 7290 in 69f30fc [3]: Searched for 'js-yaml', 'jsyaml', require/import statements, and yaml.load/dump usage patterns across all .js/.jsx/.ts files - no direct usage found in application code fossabot analyzed this PR using dependency research. View this analysis on the web |
Bumps js-yaml from 4.1.0 to 4.1.1.
Changelog
Sourced from js-yaml's changelog.
Commits
cc482e74.1.1 released50968b8dist rebuildd092d86lint fix383665ffix prototype pollution in merge (<<)0d3ca7aREADME.md: HTTP => HTTPS (#678)49baadddoc: 'empty' style option for !!nullba3460eFix demo link (#618)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.