fix(deps): upgrade lodash to 4.18.1

[snyk-io]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Arbitrary Code Injection SNYK-JS-LODASH-15869625	243
	Prototype Pollution SNYK-JS-LODASH-15869619	117

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Prototype Pollution
🦉 Arbitrary Code Injection

[snyk-io]

This minor version upgrade for lodash introduces security fixes that alter existing behavior, warranting a medium risk assessment.

Key Changes:

• _.unset / _.omit: To fix a prototype pollution vulnerability, calls attempting to traverse forbidden paths (like constructor or prototype) will now return false and not delete the property. Previously, these calls might have returned true. Code that relies on the return value of these functions for flow control may be impacted.
• _.template: To fix a code injection vulnerability, the function will now throw an "Invalid imports option" error if the imports keys contain forbidden characters. Previously, this might have been ignored.

Recommendation: While these are important security updates, the changes introduce stricter validation and modified return values. It is recommended to verify that your application's usage of _.unset, _.omit, and _.template is not affected by this stricter behavior.

Source: GitHub Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-io]

✅ This PR has been automatically closed

The security issues addressed by this pull request are no longer present in the latest project scan. All vulnerabilities this PR was created to fix have been resolved through other means (e.g., dependency updates, direct fixes, or changes in vulnerability data).

Resolved Issues

• SNYK-JS-LODASH-15869619
• SNYK-JS-LODASH-15869625

What should I do?

No action is required. If you believe this PR was closed in error, you can reopen it and contact Snyk support.

---

This action was performed automatically by Snyk.