Bump eslint-plugin-import-x in lockfile

[Mrtenz]

This fixes an issue in the compatibility tests workflow in CI (example here) since the latest version of eslint-plugin-import-x uses unrs-resolver, which needs to be added to the allow-scripts configuration. I've bumped it in the lockfile here and added the allow-scripts configuration to resolve the CI error.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​unrs/​resolver-binding-win32-x64-msvc@​1.7.11
	@​unrs/​resolver-binding-win32-arm64-msvc@​1.7.11
	@​unrs/​resolver-binding-win32-ia32-msvc@​1.7.11
	@​unrs/​resolver-binding-linux-x64-gnu@​1.7.11
	@​unrs/​resolver-binding-linux-x64-musl@​1.7.11
	@​unrs/​resolver-binding-freebsd-x64@​1.7.11
	@​unrs/​resolver-binding-linux-arm64-gnu@​1.7.11
	@​unrs/​resolver-binding-linux-arm64-musl@​1.7.11
	@​unrs/​resolver-binding-linux-arm-gnueabihf@​1.7.11
	@​unrs/​resolver-binding-linux-arm-musleabihf@​1.7.11
	@​unrs/​resolver-binding-linux-ppc64-gnu@​1.7.11
	@​unrs/​resolver-binding-linux-riscv64-gnu@​1.7.11
	@​unrs/​resolver-binding-linux-riscv64-musl@​1.7.11
	@​unrs/​resolver-binding-linux-s390x-gnu@​1.7.11
	@​unrs/​resolver-binding-darwin-arm64@​1.7.11
	@​unrs/​resolver-binding-darwin-x64@​1.7.11
	@​unrs/​resolver-binding-wasm32-wasi@​1.7.11
	stable-hash-x@​0.1.1
	@​napi-rs/​wasm-runtime@​0.2.10
	@​emnapi/​runtime@​1.4.3
	@​emnapi/​core@​1.4.3
	@​tybys/​wasm-util@​0.9.0
	@​emnapi/​wasi-threads@​1.0.2
	unrs-resolver@​1.7.11
	get-tsconfig@​4.8.1 ⏵ 4.10.1	+1		+1
	semver@​7.6.3 ⏵ 7.7.2	+1		+1
	napi-postinstall@​0.2.4
	eslint-import-context@​0.1.8
	eslint-plugin-import-x@​4.4.0 ⏵ 4.15.1	+2		+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 for details)
Block		@emnapi/core@1.4.3 has Network access. Module: globalThis["fetch"] Location: Package overview From: yarn.lock → npm/@emnapi/core@1.4.3 ℹ Read more on: This package | This alert | What is network access? 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/core@1.4.3. 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		@tybys/wasm-util@0.9.0 has Network access. Module: globalThis["fetch"] Location: Package overview From: yarn.lock → npm/@tybys/wasm-util@0.9.0 ℹ Read more on: This package | This alert | What is network access? 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@tybys/wasm-util@0.9.0. 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		@unrs/resolver-binding-wasm32-wasi@1.7.11 has Network access. Module: globalThis["fetch"] Location: Package overview From: yarn.lock → npm/@unrs/resolver-binding-wasm32-wasi@1.7.11 ℹ Read more on: This package | This alert | What is network access? 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@unrs/resolver-binding-wasm32-wasi@1.7.11. 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		napi-postinstall@0.2.4 has Network access. Module: globalThis["fetch"] Location: Package overview From: yarn.lock → npm/napi-postinstall@0.2.4 ℹ Read more on: This package | This alert | What is network access? 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/napi-postinstall@0.2.4. 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		unrs-resolver@1.7.11 has Shell access. Module: child_process Location: Package overview From: yarn.lock → npm/unrs-resolver@1.7.11 ℹ Read more on: This package | This alert | What is shell access? 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 avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. 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.7.11. 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		unrs-resolver@1.7.11 has Install scripts. Install script: postinstall Source: napi-postinstall unrs-resolver 1.7.11 check From: yarn.lock → npm/unrs-resolver@1.7.11 ℹ 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.7.11. 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