Update lockfile

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
• 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (4)

• packages/core/solidity/src/environments/hardhat/package-lock.json is excluded by !**/package-lock.json
• packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json is excluded by !**/package-lock.json
• packages/core/solidity/src/environments/hardhat/upgradeable/package-lock.json is excluded by !**/package-lock.json
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch renovate/lock-file-maintenance

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[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		Potential security risk (AI signal): npm @modelcontextprotocol/sdk is 70.0% likely risky Notes: No strong evidence of intentional malware/backdoor behavior in this code fragment (no command execution or covert remote exfiltration). However, the module contains multiple high-impact security anti-patterns: (1) it logs a user-submitted API key in plaintext, (2) it interpolates untrusted values (userSession.name and cartId) directly into HTML without escaping (XSS risk), (3) CORS is configured permissively (origin '*', credentials:true), and (4) elicitation completion appears weakly bound to the presenting MCP session/user context in the shown endpoints. Treat this as high security risk if used beyond a tightly controlled demo environment. Confidence: 0.70 Severity: 0.73 From: packages/mcp/package.json → npm/@modelcontextprotocol/sdk@1.30.0 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? 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 identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@modelcontextprotocol/sdk@1.30.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		Potential security risk (AI signal): npm @nomicfoundation/hardhat-ignition is 75.0% likely risky Notes: This module is not overtly malicious, but it creates a high-impact security risk by using execSync with a shell command string that directly interpolates a caller-provided filePath without sanitization or safe argument handling. If filePath can be influenced by an attacker, this can enable arbitrary command execution (command injection). Refactor to use non-shell execution (e.g., spawn with args) and validate/quote inputs appropriately. Confidence: 0.75 Severity: 0.70 From: packages/core/solidity/src/environments/hardhat/package-lock.json → npm/@nomicfoundation/hardhat-ignition@3.1.8 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? 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 identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@nomicfoundation/hardhat-ignition@3.1.8. 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		Potential security risk (AI signal): npm lodash-es is 80.0% likely risky Notes: No overt malware/backdoor/IO/exfiltration behavior is present in this module itself. However, it is a high-risk template compiler because it dynamically generates and compiles JavaScript via Function(...) using template-derived fragments and caller-supplied configuration. In particular, the evaluate directive inserts raw JavaScript into the generated source, and with (obj) broadens scope when variable is unset. Treat template strings and especially evaluate/interpolate content and options as fully trusted or strictly controlled; otherwise, this can enable arbitrary code execution in the context of the application. Confidence: 0.80 Severity: 0.70 From: packages/core/solidity/src/environments/hardhat/package-lock.json → npm/@nomicfoundation/hardhat-ignition-ethers@3.1.6 → npm/@nomicfoundation/hardhat-ignition@3.1.8 → npm/lodash-es@4.18.1 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? 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 identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/lodash-es@4.18.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.
Block		Potential security risk (AI signal): npm rollup is 82.0% likely risky Notes: The code intentionally enables dynamic plugin/config execution. The most concerning aspect is new Function evaluating CLI-provided plugin strings and plugin argument expressions, combined with dynamic require/import of plugin modules. If plugin/config inputs are untrusted, this becomes a direct code-execution (RCE) supply-chain attack vector. Additionally, it reads stdin into a virtual module and executes transpiled config by writing and importing generated code. No obvious steganography/obfuscation is present; the risk is primarily the dynamic execution and module loading design. Confidence: 0.82 Severity: 0.78 From: packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json → npm/@parity/hardhat-polkadot@0.2.7 → npm/rollup@4.62.4 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? 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 identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@4.62.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		Potential security risk (AI signal): npm tsx is 78.0% likely risky Notes: The primary security issue in this module is direct dynamic code execution: (0, eval) is called on substrings derived from the caller-controlled input during parsing. If parse() is ever invoked with untrusted or partially trusted input, this enables arbitrary JavaScript execution in the consumer environment. The embedded WebAssembly is opaque but also determines what content becomes evaluated and what slices are produced. No explicit exfiltration or filesystem/network activity is visible in this wrapper, but the eval sink makes the overall security posture high-risk. Confidence: 0.78 Severity: 0.90 From: packages/core/solidity/src/environments/hardhat/package-lock.json → npm/tsx@4.23.11 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? 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 identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tsx@4.23.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		Potential security risk (AI signal): npm tsx is 70.0% likely risky Notes: High-risk design for supply-chain/security review: although the core parsing is delegated to an embedded WebAssembly module, the JavaScript wrapper conditionally calls eval() on substrings derived from the untrusted input string (triggered by quote heuristics). This creates a direct path from attacker-controlled text to arbitrary JavaScript execution. Additionally, parse failures embed input excerpts into thrown errors (possible information disclosure) and large inputs can trigger WASM memory growth (DoS). This module should be treated as unsafe unless the calling context strictly guarantees that inputs are fully trusted and non-executable (or the eval behavior is removed/disabled). Confidence: 0.70 Severity: 0.86 From: packages/core/solidity/src/environments/hardhat/package-lock.json → npm/tsx@4.23.11 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? 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 identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tsx@4.23.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		Potential security risk (AI signal): npm tsx is 62.0% likely risky Notes: This module is a runtime execution hook that patches Node’s REPL eval to transform user-entered code with esbuild (including TS parsing) and rewrites require to global.require in the transformed output before executing it via the original eval. While there is no direct evidence of network exfiltration or credential theft within this snippet, the pattern is strongly suspicious because it expands execution capabilities and alters module-loading semantics at runtime, with silent error suppression reducing observability. Confidence: 0.62 Severity: 0.70 From: packages/core/solidity/src/environments/hardhat/package-lock.json → npm/tsx@4.23.11 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? 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 identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tsx@4.23.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		Potential code anomaly (AI signal): npm @babel/core is 68.0% likely to have a medium risk anomaly Notes: The code defines a stack-trace manipulation utility that can selectively hide or reveal frames and inject synthetic frames into error traces. While not inherently malicious, its global alteration of Error.prepareStackTrace and stackTraceLimit enables obfuscation of error reporting and can hinder debugging or auditing. Use is advised with thorough documentation and restricted scope in security-sensitive environments. Confidence: 0.68 Severity: 0.60 From: packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json → npm/@parity/hardhat-polkadot@0.2.7 → npm/@babel/core@7.29.7 ℹ 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/@babel/core@7.29.7. 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		Potential code anomaly (AI signal): npm @babel/core is 75.0% likely to have a medium risk anomaly Notes: The examined code is a standard, benign helper for constructing and wrapping configuration items from descriptors within Babel’s tooling. There is no evidence of data leakage, exfiltration, backdoors, or other malicious activity in this fragment. The combination of immutability, brand-based identity, and non-enumerable descriptor storage indicates a well-scoped internal utility rather than anything suspicious. Confidence: 0.75 Severity: 0.50 From: packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json → npm/@parity/hardhat-polkadot@0.2.7 → npm/@babel/core@7.29.7 ℹ 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/@babel/core@7.29.7. 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		Potential code anomaly (AI signal): npm @babel/helper-module-imports is 78.0% likely to have a medium risk anomaly Notes: The analyzed code is a Babel AST helper (ImportBuilder) used to construct import statements and interop-wrapped imports. It contains no indicators of malicious behavior, data exfiltration, backdoors, or runtime abuses. It operates within a compiler/transpiler context to produce code, not to execute arbitrary user data. Therefore, the code itself does not present security risks or malware indicators under normal usage. This is benign library behavior intended for code transformation. Confidence: 0.78 Severity: 0.55 From: packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json → npm/@parity/hardhat-polkadot@0.2.7 → npm/@babel/helper-module-imports@7.29.7 ℹ 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/@babel/helper-module-imports@7.29.7. 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		Potential code anomaly (AI signal): npm @babel/helper-module-transforms is 80.0% likely to have a medium risk anomaly Notes: The code is a legitimate, static-code transformation utility used in Babel to ensure proper behavior of ES module bindings after transforms. There is no evidence of malicious behavior, data leakage, or external communications within this fragment. It operates purely on AST-level transformations consistent with module import/export handling. Confidence: 0.80 Severity: 0.50 From: packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json → npm/@parity/hardhat-polkadot@0.2.7 → npm/@babel/helper-module-transforms@7.29.7 ℹ 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/@babel/helper-module-transforms@7.29.7. 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		Potential code anomaly (AI signal): npm @babel/helper-string-parser is 78.0% likely to have a medium risk anomaly Notes: The analyzed code is a standard, well-structured parsing utility for JavaScript string literals and escapes (consistent with Babel’s helper-string-parser). It includes thorough validation, proper Unicode handling, and defensive error reporting. There is no evidence of malicious behavior, data leakage, or network activity within this fragment. The security risk is low when used as part of a trusted toolchain; the code otherwise poses no evident supply-chain threat based on the provided snippet. Confidence: 0.78 Severity: 0.55 From: packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json → npm/@parity/hardhat-polkadot@0.2.7 → npm/@babel/helper-string-parser@7.29.7 ℹ 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/@babel/helper-string-parser@7.29.7. 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		Potential code anomaly (AI signal): npm @babel/helpers is 75.0% likely to have a medium risk anomaly Notes: The analyzed fragment is a conventional Babel/TypeScript-style decorators runtime (applyDecs) responsible for applying decorators to class members and managing metadata and initializers. There is no evidence of malware, backdoors, or external data leakage within this module. While complex, the code behaves as a metadata-driven decorator processor and should be considered low risk when used as intended. Downstream risks depend on the decorators provided by consumers, not this utility itself. Confidence: 0.75 Severity: 0.60 From: packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json → npm/@parity/hardhat-polkadot@0.2.7 → npm/@babel/helpers@7.29.7 ℹ 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/@babel/helpers@7.29.7. 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		Potential code anomaly (AI signal): npm @babel/helpers is 61.0% likely to have a medium risk anomaly Notes: The code fragment is a standard Babel decorator runtime helper (applyDecs2203). Its security posture hinges on the trustworthiness of the supplied decorators. If decorators are from untrusted sources, they can execute arbitrary code during decoration or initialization. The library itself does not exhibit malicious behavior, but this pattern introduces a high-risk surface via external inputs. Recommended mitigations include validating decorator outputs, enforcing sandboxing or runner boundaries for decorators, and auditing decorator sources in the application. Confidence: 0.61 Severity: 0.58 From: packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json → npm/@parity/hardhat-polkadot@0.2.7 → npm/@babel/helpers@7.29.7 ℹ 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/@babel/helpers@7.29.7. 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		Potential code anomaly (AI signal): npm @changesets/apply-release-plan is 62.0% likely to have a medium risk anomaly Notes: The fragment is consistent with a workspace release/changelog automation tool. No direct malware behaviors (exfiltration/crypto/mining/backdoors) are evident. However, it contains a high-sensitivity supply-chain risk: dynamically requiring and executing a changelog generator module resolved from configuration. If an attacker can influence that configuration or the resolved module path, this becomes an arbitrary code execution vector during release automation. File writes/deletes and markdown injection are secondary risks typical of such tooling. Confidence: 0.62 Severity: 0.58 From: yarn.lock → npm/@changesets/cli@2.31.1 → npm/@changesets/apply-release-plan@7.1.1 ℹ 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/@changesets/apply-release-plan@7.1.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.
Block		Potential code anomaly (AI signal): npm @grpc/grpc-js is 65.0% likely to have a medium risk anomaly Notes: The analyzed fragment is a conventional gRPC subchannel implementation featuring state management, connection orchestration, call creation with optional stats, and credential access delegation. No malicious behavior, backdoors, or data exfiltration patterns are evident in this snippet. Observability through health watchers is limited, which could reduce runtime visibility in some deployments, but does not imply security risk by itself. Confidence: 0.65 Severity: 0.58 From: packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json → npm/@parity/hardhat-polkadot@0.2.7 → npm/@grpc/grpc-js@1.14.4 ℹ 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/@grpc/grpc-js@1.14.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		Potential code anomaly (AI signal): npm @inquirer/external-editor is 70.0% likely to have a medium risk anomaly Notes: No clear evidence of intentional malware or supply-chain backdoor behavior in this fragment. The main security concern is that it launches an external editor process based on VISUAL/EDITOR (or defaults). If an attacker can control those environment variables, they may be able to execute arbitrary programs. Other behaviors (temp file creation with 'wx', read/cleanup, encoding handling) do not show obvious data theft or command injection via shell. Overall this appears to be a functional external-editor utility with an inherent environment-to-process-execution risk rather than malicious sabotage. Confidence: 0.70 Severity: 0.50 From: yarn.lock → npm/@changesets/cli@2.31.1 → npm/@inquirer/external-editor@1.0.3 ℹ 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/@inquirer/external-editor@1.0.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		Potential code anomaly (AI signal): npm @nomicfoundation/edr is 70.0% likely to have a medium risk anomaly Notes: This fragment is primarily a native/WASI binding loader with extensive OS/architecture branching. It does not show direct malware behaviors in the JavaScript layer (no network, file writes, or obvious credential theft). However, it contains a major security red flag: if NAPI_RS_NATIVE_LIBRARY_PATH can be influenced, it becomes an environment-controlled require() that can load arbitrary code/binaries at initialization. The remaining risk depends on the integrity and behavior of the loaded native/WASM modules, which are not included here. Confidence: 0.70 Severity: 0.55 From: packages/core/solidity/src/environments/hardhat/package-lock.json → npm/hardhat@3.12.0 → npm/@nomicfoundation/edr@0.15.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/@nomicfoundation/edr@0.15.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		Potential code anomaly (AI signal): npm @nomicfoundation/hardhat-utils is 66.0% likely to have a medium risk anomaly Notes: No direct malware, exfiltration, or obfuscated payload is evident in this fragment. The main risk is security/operational: it is a detached-process launcher that directly executes a caller-chosen entrypoint (including .ts via tsx/esm) with caller-provided arguments and environment, while suppressing output/errors (stdio:'ignore'). If any of absolutePathToSubProcessFile/args/env can be influenced by an attacker, this becomes a practical arbitrary code execution primitive in the spawned context. Confidence: 0.66 Severity: 0.55 From: packages/core/solidity/src/environments/hardhat/package-lock.json → npm/@nomicfoundation/hardhat-ignition-ethers@3.1.6 → npm/@nomicfoundation/hardhat-ignition@3.1.8 → npm/@nomicfoundation/hardhat-ethers@4.0.15 → npm/@openzeppelin/hardhat-upgrades@4.1.0 → npm/hardhat@3.12.0 → npm/@nomicfoundation/hardhat-utils@4.1.7 ℹ 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/@nomicfoundation/hardhat-utils@4.1.7. 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		Potential code anomaly (AI signal): npm @protobufjs/codegen is 72.0% likely to have a medium risk anomaly Notes: No direct malicious behavior (e.g., exfiltration, persistence, or credential theft) is evident in this module. However, it is inherently a dynamic code execution utility: it constructs JavaScript source from caller-influenced templates/body and scope, then executes it using the Function constructor. If any upstream input can influence templates or accumulated body, this module can enable code injection/RCE in the caller’s context. Treat as high-risk when used with untrusted data; otherwise it functions as a formatter/codegen helper. Confidence: 0.72 Severity: 0.52 From: packages/core/solidity/src/environments/hardhat/polkadot/package-lock.json → npm/@parity/hardhat-polkadot@0.2.7 → npm/@protobufjs/codegen@2.0.5 ℹ 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/@protobufjs/codegen@2.0.5. 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.
See 47 more rows in the dashboard

View full report

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: packages/ui/deno.lock

Command failed: deno install --frozen=false
�[0m�[33mWarning�[0m "importMap" field can only be specified in the workspace root deno.json file.
    at file:///tmp/renovate/repos/github/OpenZeppelin/contracts-wizard/packages/ui/deno.json
Seeded deno.lock from /tmp/renovate/repos/github/OpenZeppelin/contracts-wizard/yarn.lock
�[0m�[33mWarning�[0m Not implemented scheme 'git+https'
    at file:///tmp/renovate/repos/github/OpenZeppelin/contracts-wizard/packages/core/solidity/package.json
�[0m�[33mWarning�[0m Not implemented scheme 'git+https'
    at file:///tmp/renovate/repos/github/OpenZeppelin/contracts-wizard/packages/core/solidity/package.json
�[0m�[1m�[31merror�[0m: failed reading lockfile '/tmp/renovate/repos/github/OpenZeppelin/contracts-wizard/deno.lock'

Caused by:
    0: The lockfile is corrupt. Remove the lockfile to regenerate it.
    1: Could not find '@openzeppelin/contracts@5.5.0' in the list of packages.

File name: packages/core/confidential/src/environments/hardhat/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: hardhat-sample@0.0.1
npm error Found: @zama-fhe/relayer-sdk@0.3.0-5
npm error node_modules/@zama-fhe/relayer-sdk
npm error   dev @zama-fhe/relayer-sdk@"0.3.0-5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @zama-fhe/relayer-sdk@"^0.3.0-8" from @fhevm/mock-utils@0.3.0-4
npm error node_modules/@fhevm/mock-utils
npm error   peer @fhevm/mock-utils@"0.3.0-4" from @fhevm/hardhat-plugin@0.3.0-4
npm error   node_modules/@fhevm/hardhat-plugin
npm error     dev @fhevm/hardhat-plugin@"^0.3.0-1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-07T19_21_38_979Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-07T19_21_38_979Z-debug-0.log