chore(deps-dev): bump np from 11.2.2 to 12.0.1

[dependabot]

Bumps np from 11.2.2 to 12.0.1.

Release notes

Sourced from np's releases.

v12.0.1

• Fix npm pack with devEngines.packageManager b0ca868

---

sindresorhus/np@v12.0.0...v12.0.1

v12.0.0

Breaking

• Require Node.js 22, npm 10, pnpm 11 717080a

Improvements

• Support npm 12 (#799) 516fe4a
• Add --stage flag for staged publishing (#802) 9582dff
• Block empty publish when ignore-scripts disables the build script (#801) 6e75967
• Re-verify npm auth after auto-login (#800) 55ed2bf

---

sindresorhus/np@v11.2.2...v12.0.0

Commits

• bd2160e 12.0.1
• b0ca868 Fix npm pack with devEngines.packageManager
• 9144321 12.0.0
• 9582dff Add --stage flag for staged publishing (#802)
• 717080a Require Node.js 22, npm 10, pnpm 11
• 6e75967 Block empty publish when ignore-scripts disables the build script (#801)
• 55ed2bf Re-verify npm auth after auto-login (#800)
• 516fe4a Support npm 12 (#799)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codeant-ai]

Skipping PR review because a bot author is detected.

If you want to trigger CodeAnt AI, comment @codeant-ai review to trigger a manual review.

[codereviewbot-ai]

🤖 Review skipped: reviews for bot-created pull requests are not allowed on free accounts. Upgrade to a paid plan to enable bot reviews.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​np@​12.0.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm execa is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/np@12.0.1 → npm/execa@9.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: 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@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/execa@9.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm wrap-ansi is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/np@12.0.1 → npm/wrap-ansi@3.0.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: 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@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/wrap-ansi@3.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report