Update dependency @types/mocha to v10.0.10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/mocha (source)	10.0.6 → 10.0.10

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[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. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		viem@1.21.4 has Telemetry. Note: The code seems to be related to URI manipulation and validation, but the use of dynamic image loading could be an attempt to obfuscate network communication, raising potential security concerns. From: ? → npm/@wagmi/connectors@3.1.11 → npm/viem@1.21.4 ℹ Read more on: This package | This alert | What is telemetry? 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: Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/viem@1.21.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		viem@2.0.0 has Telemetry. Note: The code seems to be related to URI manipulation and validation, but the use of dynamic image loading could be an attempt to obfuscate network communication, raising potential security concerns. From: ? → npm/@celo/rainbowkit-celo@1.1.1 → npm/wagmi@1.4.13 → npm/@wagmi/connectors@3.1.11 → npm/viem@2.0.0 ℹ Read more on: This package | This alert | What is telemetry? 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: Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/viem@2.0.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		@walletconnect/core@2.11.0 is a AI-detected potential code anomaly. Notes: The fragment demonstrates a legitimate attestation/verification subsystem using an embedded iframe and cross-origin messaging with persistent expiration management. The main security vulnerabilities stem from cross-origin messaging with an insecure wildcard in postMessage and reliance on external attestation endpoints. Harden cross-origin messaging by specifying exact targetOrigin, validating message sources, and restricting data exchanged via postMessage. Add input validation for attestationId/verifyUrl and minimize sensitive data in logs. Overall risk is medium; malware likelihood is low unless combined with insecure deployment practices. Confidence: 1.00 Severity: 0.60 From: ? → npm/@wagmi/connectors@3.1.11 → npm/@walletconnect/core@2.11.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@walletconnect/core@2.11.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		viem@2.34.0 is a AI-detected potential code anomaly. Notes: The code implements a cross-chain deposit flow with proper validations, artifact reads, and on-chain interactions. There is no evidence of hidden backdoors, data exfiltration, or malware. The main security considerations relate to token approval logic and correct configuration of flags to avoid granting excessive allowances. Overall, the module appears legitimate for a bridge deposit flow, with moderate risk primarily around configuration of approvals and correct handling of gas/fees. Confidence: 1.00 Severity: 0.60 From: ? → npm/@wagmi/connectors@3.1.11 → npm/viem@2.34.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/viem@2.34.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.

View full report

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​celo/​rainbowkit-celo@​1.1.1
	@​jridgewell/​set-array@​1.1.2
	any-promise@​1.3.0
	pify@​4.0.1 ⏵ 2.3.0
	@​jridgewell/​resolve-uri@​3.1.0
	thenify@​3.3.1
	wagmi@​1.4.13
	thenify-all@​1.6.0
	@​celo/​abis@​10.0.0
	@​wagmi/​connectors@​3.1.11
	@​jridgewell/​sourcemap-codec@​1.4.15
	@​jridgewell/​trace-mapping@​0.3.18
	typescript@​5.9.2 ⏵ 5.0.4	+1

View full report