fix(deps): pin ajv, ajv-formats, multer, and busboy

[jnylin]

to resolve vulnerabilities

Address multiple security vulnerabilities in nested dependencies by forcing safer versions using Yarn resolutions.

• Fixes ReDoS vulnerability in ajv by upgrading to v8.
• Upgrades ajv-formats to v2 to ensure compatibility with ajv v8 and prevent runtime crashes.
• Bypasses the high-severity dicer vulnerability by forcing multer and busboy to safe versions.

Closes #461

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	multer@​1.4.4 ⏵ 1.4.5-lts.2	+1
	jest-environment-node@​30.3.0 ⏵ 30.4.1	+1		+1
	jest@​30.3.0 ⏵ 30.4.2	+1		+1
	babel-jest@​30.3.0 ⏵ 30.4.1
	fs-extra@​8.1.0 ⏵ 11.3.5	+1
	tmp@​0.2.5 ⏵ 0.2.7	+1	+16	+1
	express@​4.22.1 ⏵ 4.22.2	+1
	jest-mock@​30.3.0 ⏵ 30.4.1	+1		+1
	puppeteer@​24.42.0 ⏵ 24.43.1
	i18next@​26.0.7 ⏵ 26.3.3
	uuid@​11.1.0 ⏵ 11.1.1	+1	+2	+1
	electron@​41.3.0 ⏵ 41.9.0	+1		+1
	taze@​19.11.0 ⏵ 19.14.1	+1			+2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/puppeteer@24.43.1 → npm/js-yaml@4.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm puppeteer-core is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/puppeteer@24.43.1 → npm/puppeteer-core@24.43.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/puppeteer-core@24.43.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/jest@30.4.2 → npm/puppeteer@24.43.1 → npm/i18next-json-sync@3.1.2 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[jnylin]

Pinned multer to 1.4.5-lts.2 to resolve the core vulnerabilities. Note that the socket security still flag this package due to legacy CVE mappings, but this is currently the highest available security level for the 1.x branch.

[jnylin]

@SocketSecurity ignore npm/puppeteer-core@24.43.1