Updating packages

[Pasha Zayko (pasha-zayko)]

Packages updated and lock file regenerated

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​16.1.6 ⏵ 16.2.6		+75	+1
	eslint-config-next@​16.1.6 ⏵ 16.2.6
	typescript-eslint@​8.56.0 ⏵ 8.59.4	+1		+1
	@​stylistic/​eslint-plugin@​5.8.0 ⏵ 5.10.0
	eslint-plugin-jsdoc@​62.6.0 ⏵ 62.6.1	-9			+6
	@​eslint/​js@​9.39.2 ⏵ 9.39.4
	eslint@​9.39.2 ⏵ 9.39.4	+1
	mocha@​11.7.5 ⏵ 11.7.6	+3		+1
	eslint-plugin-react-hooks@​7.0.1 ⏵ 7.1.1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Recently published: npm mocha published 10 hours ago Location: Package overview From: package-lock.json → npm/mocha@11.7.6 ℹ Read more on: This package | This alert | What are recently published artifacts? 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 either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/mocha@11.7.6. 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.
Block		Recently published: npm node-releases published 17 hours ago Location: Package overview From: package-lock.json → npm/eslint-plugin-react-hooks@7.1.1 → npm/node-releases@2.0.45 ℹ Read more on: This package | This alert | What are recently published artifacts? 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 either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-releases@2.0.45. 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.
Block		Recently published: npm semver published 3 hours ago Location: Package overview From: package-lock.json → npm/eslint-plugin-jsdoc@62.6.1 → npm/eslint-config-next@16.2.6 → npm/next@16.2.6 → npm/typescript-eslint@8.59.4 → npm/semver@7.8.1 ℹ Read more on: This package | This alert | What are recently published artifacts? 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 either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/semver@7.8.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		Potential vulnerability: npm next with risk level "medium" Location: Package overview From: package-lock.json → npm/next@16.2.6 ℹ Read more on: This package | This alert | Navigating potential vulnerabilities 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: It is advisable to proceed with caution. Engage in a review of the package's security aspects and consider reaching out to the package maintainer for the latest information or patches. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@16.2.6. 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		Potential vulnerability: npm picomatch with risk level "medium" Location: Package overview From: package-lock.json → npm/eslint-config-next@16.2.6 → npm/picomatch@2.3.2 ℹ Read more on: This package | This alert | Navigating potential vulnerabilities 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: It is advisable to proceed with caution. Engage in a review of the package's security aspects and consider reaching out to the package maintainer for the latest information or patches. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/picomatch@2.3.2. 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		Install-time scripts: npm unrs-resolver during postinstall Install script: postinstall Source: node postinstall.js From: package-lock.json → npm/eslint-config-next@16.2.6 → npm/unrs-resolver@1.12.2 ℹ Read more on: This package | This alert | What is an install script? 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 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/unrs-resolver@1.12.2. 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

[Copilot]

Pull request overview

This PR updates the repository’s Node.js tooling dependencies (lint/test/framework packages) and regenerates the npm lockfile to reflect the new resolved versions.

Changes:

• Bump the declared npm package manager version to npm@11.15.0.
• Update key dependencies/devDependencies (notably @stylistic/eslint-plugin, eslint-config-next, eslint-plugin-react-hooks, typescript-eslint, mocha, next).
• Regenerate package-lock.json with the resulting transitive dependency updates.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
package.json	Updates the declared package manager and bumps a small set of direct dependency versions.
package-lock.json	Regenerated lockfile capturing updated direct + transitive dependency resolutions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.