Skip to content

[Snyk] Security upgrade xo from 0.45.0 to 0.46.0#141

Open
lholmquist wants to merge 1 commit into
mainfrom
snyk-fix-69585a5f7165dca9abd5686ce64aabdb
Open

[Snyk] Security upgrade xo from 0.45.0 to 0.46.0#141
lholmquist wants to merge 1 commit into
mainfrom
snyk-fix-69585a5f7165dca9abd5686ce64aabdb

Conversation

@lholmquist

Copy link
Copy Markdown
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Uncontrolled resource consumption
SNYK-JS-BRACES-6838727
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Inefficient Regular Expression Complexity
SNYK-JS-MICROMATCH-6838728
No No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: xo The new version differs by 5 commits.
  • b9ce6c8 0.46.0
  • dddc991 Upgrade to ESLint 8
  • 431887d Group files by config (#622)
  • c9bbfb1 Fix installing XO on npm 6 by bundling TS-dependent dependencies to avoid hoisting (#624)
  • eefd88a Clarify Prettier defaulting behavior (#616)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncontrolled resource consumption

@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 91.045%. remained the same
when pulling 2eef0a1 on snyk-fix-69585a5f7165dca9abd5686ce64aabdb
into 0a9dbf3 on main.

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.

3 participants