chore(deps): update dependency ts-node to ^10.9.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ts-node (source)	^10.9.1 -> ^10.9.2

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
dev-astral	Ready	Preview	Comment	Sep 1, 2025 6:20pm
explorer	Ready	Preview	Comment	Sep 1, 2025 6:20pm

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	form-data@​4.0.2
	@​nx/​nx-darwin-arm64@​20.5.0
	@​nx/​nx-darwin-x64@​20.5.0
	@​nx/​nx-freebsd-x64@​20.5.0
	@​nx/​nx-linux-arm-gnueabihf@​20.5.0
	@​nx/​nx-linux-arm64-gnu@​20.5.0
	@​nx/​nx-linux-arm64-musl@​20.5.0
	@​nx/​nx-linux-x64-gnu@​20.5.0
	@​nx/​nx-linux-x64-musl@​20.5.0
	@​nx/​nx-win32-arm64-msvc@​20.5.0
	@​nx/​nx-win32-x64-msvc@​20.5.0
	@​types/​ioredis@​5.0.0
	nx@​20.5.0
	is-unicode-supported@​0.1.0
	hasown@​2.0.2
	is-interactive@​1.0.0
	has-tostringtag@​1.0.2
	isarray@​2.0.5 ⏵ 1.0.0	+1		+21
	safer-buffer@​2.1.2
	typedarray@​0.0.6
	path-parse@​1.0.7
	indent-string@​4.0.0
	gopd@​1.2.0
	es-define-property@​1.0.1
	es-set-tostringtag@​2.1.0
	@​npmcli/​name-from-folder@​2.0.0
	is-core-module@​2.16.1
	function-bind@​1.1.2
	safe-buffer@​5.1.2
	fs-constants@​1.0.0
	is-arrayish@​0.2.1
	@​npmcli/​node-gyp@​3.0.0
	unique-slug@​4.0.0
See 403 more rows in the dashboard

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		[email protected] is Known malware. Note: The code is not obviously malicious (no obfuscation, no eval, no hardcoded secrets), but it contains a high-risk archive extraction vulnerability: tar entry names from the downloaded archive are used directly to construct output paths without sanitization, allowing path traversal and arbitrary file writes if an attacker controls the downloaded archive or the download URL. This creates a significant supply-chain risk if an attacker can supply a malicious tarball. Remediation: validate/sanitize headers.name (reject absolute paths, normalize and ensure the final path stays inside the bundleExtractLocation), disallow symlinks or special files, and validate archive contents (e.g., check expected file list or signed manifests) before writing. Overall: not malware in itself but presents a serious security vulnerability for supply-chain attacks. From: indexers/yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is known malware? 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: It is strongly recommended that malware is removed from your codebase. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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		[email protected] has a Critical CVE. CVE: GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary (CRITICAL) Affected versions: < 2.5.4; >= 3.0.0 < 3.0.4; >= 4.0.0 < 4.0.4 Patched version: 4.0.4 From: indexers/db/yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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		[email protected] has a Critical CVE. CVE: GHSA-cchq-frgv-rjh5 vm2 Sandbox Escape vulnerability (CRITICAL) Affected versions: <= 3.9.19 Patched version: No patched versions From: ? → npm/@subql/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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		[email protected] has a Critical CVE. CVE: GHSA-g644-9gfx-q4q4 vm2 Sandbox Escape vulnerability (CRITICAL) Affected versions: <= 3.9.19 Patched version: No patched versions From: ? → npm/@subql/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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		@webbuf/[email protected] has Obfuscated code. Confidence: 0.90 Location: Package overview From: ? → npm/@autonomys/[email protected] → npm/@webbuf/[email protected] ℹ 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 [email protected]. 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/@webbuf/[email protected]. 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		[email protected] has Obfuscated code. Confidence: 0.94 Location: Package overview From: explorer/yarn.lock → npm/[email protected] ℹ 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 [email protected]. 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/[email protected]. 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