Skip to content

[Snyk] Security upgrade aegir from 37.12.1 to 47.0.26#185

Open
adamlaska wants to merge 1 commit into
masterfrom
snyk-fix-d3fdb39e1eb40ca429aabb0bfd7d5071
Open

[Snyk] Security upgrade aegir from 37.12.1 to 47.0.26#185
adamlaska wants to merge 1 commit into
masterfrom
snyk-fix-d3fdb39e1eb40ca429aabb0bfd7d5071

Conversation

@adamlaska

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 5 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Improper Handling of Unicode Encoding
SNYK-JS-TAR-15038581
  713  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-DIFF-14917201
  708  
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  693  
medium severity Uncontrolled Recursion
SNYK-JS-ESLINT-15102420
  623  
medium severity Directory Traversal
SNYK-JS-TAR-15127355
  596  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Directory Traversal

@google-cla

google-cla Bot commented Jan 29, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants