fix(deps): Update dependency mendoza to v3.0.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
mendoza (source)	3.0.5 -> 3.0.7

---

Release Notes

sanity-io/mendoza-js (mendoza)

v3.0.7

Compare Source

Bug Fixes

• install snippets in README (19d0c17)

v3.0.6

Compare Source

Bug Fixes

• deps: update dependency @​sanity/pkg-utils to ^5.0.4 (#​55) (6479553)

---

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/groq-js@1.4.3	network	0	610 kB	sanity-io
npm/groq@3.34.0	None	0	8.83 kB	ricokahler
npm/husky@8.0.3	environment, filesystem, shell	0	6.44 kB	typicode
npm/lint-staged@14.0.1	Transitive: environment, filesystem, shell	+12	791 kB	okonet
npm/ls-engines@0.9.1	Transitive: environment, eval, filesystem, network, shell	+166	7.84 MB	ljharb

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Potential typo squat	npm/is-node@0.0.0	Did you mean: its-node (509 times more downloads)	package-lock.json package.json

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/is-node@0.0.0