chore(deps): update dependency eslint-config-sanity to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-sanity (source)	^6.0.0 -> ^7.1.2

---

Release Notes

sanity-io/eslint-config-sanity (eslint-config-sanity)

v7.1.2

Compare Source

Bug Fixes

• remove react/prop-types rule (89b18d4)

v7.1.1

Compare Source

Bug Fixes

• better typescript defaults (b3f47c4)

v7.1.0

Compare Source

Features

• add support for react hooks (7a3034f)

Bug Fixes

• add support for simple-import-sort (30b6b50)

v7.0.3

Compare Source

Bug Fixes

• remove deprecated rules (5b4477a)
• remove more deprecated rules (bd823f4)

v7.0.2

Compare Source

Bug Fixes

• deps: Update linters to v7 (#​61) (3064a8b)

v7.0.1

Compare Source

Bug Fixes

• don't publish junk files (#​54) (59607e6)

v7.0.0

Compare Source

⚠ BREAKING CHANGES

• extend recommended defaults (#​53)

Features

• extend recommended defaults (#​53) (2ffca7d)

Bug Fixes

• move to release please (2fcb859)

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
gatsby-source-sanity	❌ Failed (Inspect)			Mar 18, 2024 4:22pm

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+581	285 MB	pieh
npm/[email protected]	None	+1	97.1 kB	keyanzhang
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+222	29.5 MB	simenb

🚮 Removed packages: npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

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
Protestware/Troll package	npm/[email protected]	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: postinstall Source: node -e "try{require('./_postinstall')}catch(e){}" || exit 0	orphan: npm/[email protected]
Native code	npm/@parcel/[email protected]	Location: Package overview	examples/cdrs/package-lock.json examples/cdrs/package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: node src/postinstall.js || true	examples/cdrs/package-lock.json examples/cdrs/package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: node scripts/postinstall.js	examples/cdrs/package-lock.json examples/cdrs/package.json

View full report↗︎

Next steps

What is protestware?

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package my come along with functionality unrelated to its primary purpose.

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@parcel/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]