chore(deps): update dependency prettier-plugin-packagejson to ^2.4.12

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
prettier-plugin-packagejson	^2.4.6 -> ^2.4.12

---

Release Notes

matzkoh/prettier-plugin-packagejson (prettier-plugin-packagejson)

v2.4.12

Compare Source

Bug Fixes

• deps: update dependency sort-package-json to v2.8.0 (8991b5b)

v2.4.11

Compare Source

Bug Fixes

• .js to .cjs for compatibility with { "type": "module" } (ac3a006)

v2.4.10

Compare Source

Bug Fixes

• deps: update dependency sort-package-json to v2.7.0 (0d520e3)

v2.4.9

Compare Source

Bug Fixes

• deps: update dependency synckit to v0.9.0 (446d477)

v2.4.8

Compare Source

Bug Fixes

• deps: update dependency synckit to v0.8.8 (bfbbf2d)

v2.4.7

Compare Source

Bug Fixes

• deps: update dependency synckit to v0.8.6 (7637443)

---

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

[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, shell, unsafe	+56	9.2 MB	lydell
npm/[email protected]	Transitive: environment, eval, filesystem, shell, unsafe	+117	17.8 MB	sanity-io
npm/[email protected]	Transitive: environment, eval, filesystem, shell, unsafe	+56	9.25 MB	jounqin
npm/[email protected]	filesystem Transitive: environment, eval, shell, unsafe	+100	13.3 MB	ljharb
npm/[email protected]	Transitive: environment, eval, filesystem, shell, unsafe	+56	9.22 MB	lydell
npm/[email protected]	environment, filesystem Transitive: eval, shell, unsafe	+55	9.18 MB	eslintbot
npm/[email protected]	None	0	13 kB	esp
npm/[email protected]	network	0	734 kB	sanity-io
npm/[email protected]	None	0	8.43 kB	binoy14
npm/[email protected]	environment, filesystem, shell	0	6.44 kB	typicode
npm/[email protected]	Transitive: environment, filesystem, shell	+13	835 kB	okonet
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell	+165	7.71 MB	ljharb

🚮 Removed packages: 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
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	package-lock.json package.json
Potential typo squat	npm/[email protected]	Did you mean: its-node (514 times more downloads)	package-lock.json package.json

View full report↗︎

Next steps

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

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