🤖 Dep Updates: bump @npmcli/package-json from 7.0.0 to 7.0.4

[dependabot]

Bumps @npmcli/package-json from 7.0.0 to 7.0.4.

Release notes

Sourced from @​npmcli/package-json's releases.

v7.0.4

7.0.4 (2025-11-20)

Dependencies

• e33b13e #167 bump glob from 12.0.0 to 13.0.0 (#167) (@​dependabot[bot])

v7.0.3

7.0.3 (2025-11-18)

Bug Fixes

• 57952b8 #164 prevent crash when expanding directories.bin without filesystem path (#164) (@​MaxBlack-dev, Max Black)

Dependencies

• ba5c736 #165 bump glob from 11.1.0 to 12.0.0 (#165) (@​dependabot[bot])

v7.0.2

7.0.2 (2025-10-30)

Bug Fixes

• 7f3afb6 #156 comment typo (#156) (@​Clozent)

Dependencies

• 0393243 #160 bump proc-log from 5.0.0 to 6.0.0 (#160) (@​dependabot[bot])
• f3c7926 #161 bump json-parse-even-better-errors from 4.0.0 to 5.0.0 (#161) (@​dependabot[bot])

Chores

• 4a80b15 #162 bump @​npmcli/eslint-config from 5.1.0 to 6.0.0 (#162) (@​dependabot[bot])
• e093242 #163 bump @​npmcli/template-oss from 4.27.1 to 4.28.0 (#163) (@​dependabot[bot], @​npm-cli-bot)

v7.0.1

7.0.1 (2025-09-17)

Dependencies

• 1364087 #153 @npmcli/[email protected] (#153)

Changelog

Sourced from @​npmcli/package-json's changelog.

7.0.4 (2025-11-20)

Dependencies

• e33b13e #167 bump glob from 12.0.0 to 13.0.0 (#167) (@​dependabot[bot])

7.0.3 (2025-11-18)

Bug Fixes

• 57952b8 #164 prevent crash when expanding directories.bin without filesystem path (#164) (@​MaxBlack-dev, Max Black)

Dependencies

• ba5c736 #165 bump glob from 11.1.0 to 12.0.0 (#165) (@​dependabot[bot])

7.0.2 (2025-10-30)

Bug Fixes

• 7f3afb6 #156 comment typo (#156) (@​Clozent)

Dependencies

• 0393243 #160 bump proc-log from 5.0.0 to 6.0.0 (#160) (@​dependabot[bot])
• f3c7926 #161 bump json-parse-even-better-errors from 4.0.0 to 5.0.0 (#161) (@​dependabot[bot])

Chores

• 4a80b15 #162 bump @​npmcli/eslint-config from 5.1.0 to 6.0.0 (#162) (@​dependabot[bot])
• e093242 #163 bump @​npmcli/template-oss from 4.27.1 to 4.28.0 (#163) (@​dependabot[bot], @​npm-cli-bot)

7.0.1 (2025-09-17)

Dependencies

• 1364087 #153 @npmcli/[email protected] (#153)

Commits

• 87a5995 chore: release 7.0.4 (#168)
• e33b13e deps: bump glob from 12.0.0 to 13.0.0 (#167)
• 6204a38 chore: release 7.0.3 (#166)
• 57952b8 fix: prevent crash when expanding directories.bin without filesystem path (#164)
• ba5c736 deps: bump glob from 11.1.0 to 12.0.0 (#165)
• 8e979b3 chore: release 7.0.2 (#157)
• e093242 chore: bump @​npmcli/template-oss from 4.27.1 to 4.28.0 (#163)
• 4a80b15 chore: bump @​npmcli/eslint-config from 5.1.0 to 6.0.0 (#162)
• 0393243 deps: bump proc-log from 5.0.0 to 6.0.0 (#160)
• f3c7926 deps: bump json-parse-even-better-errors from 4.0.0 to 5.0.0 (#161)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​npmcli/package-json since your current version.

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​npmcli/​package-json@​7.0.0 ⏵ 7.0.4				+6

View full report

[socket-security-staging]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​npmcli/​package-json@​7.0.0 ⏵ 7.0.4				+3

View full report

[socket-security-staging]

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		License policy violation: npm glob under BlueOak-1.0.0 License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (npm metadata) License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/LICENSE.md) License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/@npmcli/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? 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 [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity-Staging ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity-Staging ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm glob under BlueOak-1.0.0 License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (npm metadata) License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/LICENSE.md) License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/@npmcli/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? 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 [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity-Staging ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity-Staging ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm minimatch under BlueOak-1.0.0 License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (npm metadata) License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/LICENSE.md) License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/[email protected] → npm/[email protected] → npm/@npmcli/[email protected] → npm/[email protected] → npm/@npmcli/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? 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 [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity-Staging ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity-Staging ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm path-scurry under BlueOak-1.0.0 License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (npm metadata) License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/LICENSE.md) License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/@npmcli/[email protected] → npm/@npmcli/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? 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 [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity-Staging ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity-Staging 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

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.