chore(safe): upgrade form-data to 4.0+ to fix CVE-2023-50498 QA-237

[zzzboo]

upgrade form-data to 4.0

Summary by CodeRabbit

• Chores
  • Updated internal package configuration to use a specific version of a dependency. No impact on user-facing features.

[coderabbitai]

Walkthrough

A new "overrides" section was added to the vue/package.json file, directing the package manager to resolve the "form-data" dependency specifically to version "^4.0.0". No other modifications were made to dependencies, scripts, or configurations.

Changes

Cohort / File(s)	Change Summary
Dependency Version Override vue/package.json	Added an "overrides" section to enforce "form-data" version "^4.0.0".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop and a skip, a version override,
Now "form-data" is neatly supplied.
With "^4.0.0" in our warren's den,
The package stays current, again and again.
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch hotfix-main/update-form-data-QA-237

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

vue/package.json (1)

40-41: Consider adding a Yarn fallback for teams not using npm ≥8.

"overrides" is an npm-specific field.
If any consumers of this repo rely on Yarn ≤1 they will ignore it and still get the vulnerable version.
Providing a parallel "resolutions" entry keeps both ecosystems safe.

Example:

   "overrides": {
     "form-data": "^4.0.0"
+  },
+  "resolutions": {
+    "form-data": "^4.0.0"
   }

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3356dae and e1e907e.

📒 Files selected for processing (1)

• vue/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test

🔇 Additional comments (1)

vue/package.json (1)

39-42: Add the regenerated lock-file to guarantee the override is applied in CI/CD.

npm overrides only take effect after a fresh npm install, which rewrites package-lock.json.
Without committing that updated lock-file the build pipeline (and future developers) may still resolve a vulnerable <4 version.

Action items

# after running `npm install` locally
+git add package-lock.json

Please confirm that the updated lock-file now pins form-data to ^4.0.0 in the resolved tree.