[Snyk] Security upgrade lodash from 4.17.11 to 4.18.1

[msant262]

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

Snyk changed the following file(s):

• supply_chain_security/package.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

[msant262]

This is a minor version upgrade for lodash that primarily includes security patches and bug fixes.

Potential Breaking Changes:
While this is not a major version change, the security fixes introduce behavioral changes that could impact applications relying on the previous, insecure behavior:

• _.unset / _.omit: These methods have been patched to prevent prototype pollution. Calls that attempt to modify a constructor or prototype path will now return false instead of true and will not delete the property.
• _.template: This method now has stricter validation on the imports option to prevent code injection. An error will be thrown if invalid characters are used.

Recommendation:
These changes are unlikely to affect most applications, but because they alter return values and error handling for specific edge cases, this upgrade is rated as medium risk. It is recommended to verify that your application does not rely on the old, insecure behavior of these functions.

Source: GitHub Releases

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

[msant262]

✅ 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

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