[Snyk] Security upgrade egg from 1.21.0 to 3.16.0

[atian25]

Snyk has created this PR to fix 2 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
	Server-side Request Forgery (SSRF) SNYK-JS-IP-12704893	788
	Server-side Request Forgery (SSRF) SNYK-JS-IP-12761655	788

---

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:

🦉 Server-side Request Forgery (SSRF)

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-202cc3af5d41a9b452db5dec9d4c5bc0

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @atian25, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the egg framework dependency. This update specifically targets and resolves two high-severity Server-side Request Forgery (SSRF) vulnerabilities, ensuring the application benefits from the latest security patches and stability improvements.

Highlights

• Security Upgrade: This pull request performs a security upgrade for the egg package, addressing critical vulnerabilities.
• Vulnerability Fixes: It fixes two high-severity Server-side Request Forgery (SSRF) vulnerabilities, identified as SNYK-JS-IP-12704893 and SNYK-JS-IP-12761655.
• Dependency Update: The egg dependency has been upgraded from version ^1.0.0-rc.3 to ^3.16.0.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	egg@​1.21.0 ⏵ 3.31.0			-3	+9

View full report

[gemini-code-assist]

Code Review

This PR from Snyk addresses important security vulnerabilities by upgrading the egg framework. However, this is a major version upgrade from v1 to v3, which introduces significant breaking changes. The project will not build or run correctly without also updating several other dependencies (like egg-bin and egg-mock) and the required Node.js version. I have left a critical comment on the package.json change detailing the necessary adjustments to ensure the project remains functional after this upgrade.

[gemini-code-assist]

Upgrading egg from ^1.0.0-rc.3 to ^3.16.0 is a major version jump (v1 to v3) that introduces significant breaking changes. This will break the project unless other dependencies are also updated.

Here are the critical changes required for this upgrade to work:

1. Node.js Version: egg v3 requires Node.js ^16.17.0 || ^18.12.0 || >=20.0.0. The engines field in package.json (line 33) must be updated. I recommend:

   "engines": {
     "node": ">=16.0.0"
   }

2. Development Dependencies: The devDependencies (lines 22-31) are incompatible with egg v3. They need to be upgraded. For example:

   • egg-bin: ^2.4.0 -> ^5.x
   • egg-mock: ^3.2.0 -> ^5.x
   • eslint-config-egg: ^3.2.0 -> ^12.x

3. Other egg Plugins: The other egg plugins in dependencies (lines 17-20) are also likely incompatible and will need to be updated to their latest versions compatible with egg v3. This includes egg-alinode, egg-mysql, egg-oss, and egg-view-nunjucks.

Merging this PR as-is will result in a broken build. It is strongly recommended to address these dependency incompatibilities as part of this PR to keep the main branch stable.