Update dependency prettier-plugin-packagejson to v2.5.10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
prettier-plugin-packagejson	2.5.7 -> 2.5.10

---

Release Notes

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

v2.5.10

Compare Source

v2.5.9

Compare Source

Bug Fixes

• deps: update dependency sort-package-json to v2.15.0 (0f3dd4b)

v2.5.8

Compare Source

Bug Fixes

• deps: update dependency sort-package-json to v2.14.0 (fe3557e)

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,every weekend,before 5am every weekday" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/prettier-plugin-packagejson@2.5.7 ➜ 2.5.10	Transitive: environment, filesystem	+12	374 kB	matzkoh

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	CI
Dynamic require	npm/prettier-plugin-packagejson@2.5.10	Location: Package overview	package-lock.json package.json	🚫

View full report↗︎

Next steps

What is dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.

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/prettier-plugin-packagejson@2.5.10