[Snyk] Security upgrade lodash from 4.17.21 to 4.17.23

[TimCrooker]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• packages/youtill/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-LODASH-15053838	631

---

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

[Copilot]

Pull request overview

This PR attempts to upgrade the lodash dependency from version 4.17.21 to 4.17.23 to address a medium severity prototype pollution vulnerability (SNYK-JS-LODASH-15053838, score: 631). The upgrade was automatically created by Snyk's security scanning service.

Changes:

• Updates lodash version from ^4.17.21 to ^4.17.23 in the youtill package dependencies

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The PR description indicates that the yarn.lock file failed to update automatically. This is a critical blocker because without an updated yarn.lock file, the dependency resolution will not be properly locked, and the security fix will not be reliably applied across all environments. The yarn.lock must be updated manually before this PR can be merged to ensure consistent dependency resolution.

Suggested change

	"lodash": "^4.17.23",
	"lodash": "4.17.23",