Migration of hardhat-upgrade to plugin to use hardhat v3 #1194

afa7789 · 2025-10-20T17:14:18Z

Looking to upgrade to Hardhat 3 with ESM module structure and the new plugin hooks architecture.

The migration includes updating all dependencies to Hardhat 3 compatible versions, converting the package to ESM with updated TypeScript configuration, and refactoring from the legacy extendEnvironment pattern to Hardhat 3's plugin hooks.

Several items are still in progress:

hardhat-verify in etherscan-api.ts and verify-proxy.ts,

determining the correct task usage between TASK_COMPILE_SOLIDITY and TASK_COMPILE_SOLIDITY_COMPILE ( still no clue on this )

validating the plugin hooks implementation and type extensions for the new
architecture.

After that I can try to update defender part in this plugin to the new version of hardhat as well.

Another issue, I'm not sure yet, is how to make both versions work on the same package. ( my decision on it would be to keep both as separate packages, since hardhat3 version will not be usable by v2 users.

packages changes and initial config in accord to migration documentation.

…rrors for ESM structure.

importing errors + a few todos, change of Imports + new functions to use hardhat3 library in plugin files.

…ig for NodeNext module resolution

ericglau · 2025-10-21T22:45:38Z

packages/plugin-hardhat/src/index.ts

@@ -1,29 +1,37 @@
 /* eslint-disable @typescript-eslint/no-var-requires */
+// TODO figure out what is the newer, TASK_COMPILE_SOLIDITY and TASK_COMPILE_SOLIDITY_COMPILE


These are Hardhat internal subtasks, where Hardhat calls TASK_COMPILE_SOLIDITY -> TASK_COMPILE_SOLIDITY_COMPILE_JOBS -> TASK_COMPILE_SOLIDITY_COMPILE_JOB -> TASK_COMPILE_SOLIDITY_COMPILE. And only certain parts of those need to be overridden in our plugin. See https://github.com/NomicFoundation/hardhat/blob/09951afd78e49465f7949478919c9217a12e8338/packages/hardhat-core/src/builtin-tasks/compile.ts#L1366 for the v2 internal subtasks.

We may need to find the equivalents in v3.

On it already.

it seems that there is no such function named subtask anymore, so I'm trying to find what is the alternative right now, so we can figure out how to do what we did before but in hardhat3.

…xtensions for Hardhat compatibility ( still have to test it )

…nhance artifact cleanup process

…out support in Solidity hooks

…ns for defender integration

socket-security · 2025-10-22T19:23:22Z

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		High CVE: npm `glob` CLI: Command injection via -c/--cmd executes matches with shell:true CVE: GHSA-5j98-mcp5-4vw2 glob CLI: Command injection via -c/--cmd executes matches with shell:true (HIGH) Affected versions: >= 11.0.0 < 11.1.0; >= 10.2.0 < 10.5.0 Patched version: 10.5.0 From: `?` → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is a 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 high severity 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.
Block		Potential code anomaly (AI signal): npm `acorn` is 100.0% likely to have a medium risk anomaly Notes: Overall, the analyzed code is a legitimate, well-structured Acorn 8.x parser fragment with robust handling for ES2020+ features. There is no direct malicious payload, backdoor, or exfiltration mechanism within this fragment. The primary security considerations relate to safe handling of untrusted input to avoid DoS via complex/ pathological RegExp usage or verbose error reporting. In a typical extension usage, isolate parsing to a sandbox and limit resource usage to mitigate potential abuse. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/[email protected]` → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		Potential code anomaly (AI signal): npm `consola` is 100.0% likely to have a medium risk anomaly Notes: The analyzed code fragment is a feature-rich, standard Consola logging utility responsible for redirecting and managing log output with throttling, pausing, and reporter integration. There is no direct evidence of malicious activity, hardcoded secrets, or exfiltration within this snippet. However, the powerful I/O overrides pose privacy and data flow risks if reporters or downstream sinks are untrusted. The security posture hinges on trusted reporters and proper governance of the overall supply chain. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/[email protected]` → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		Potential code anomaly (AI signal): npm `foreground-child` is 100.0% likely to have a medium risk anomaly Notes: The code implements a standard watchdog for child-process lifecycle management, aiming to prevent zombie processes when the parent exits. It is not inherently malicious, but reliability hinges on the correctness of the inline watchdog script and proper scoping of the PID. Potential improvements include addressing syntax reliability of the inline code, removing unnecessary no-op keepalive, and ensuring strict validation of the provided PID to mitigate accidental termination of unrelated processes. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/[email protected]` → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		Potential code anomaly (AI signal): npm `glob` is 100.0% likely to have a medium risk anomaly Notes: The analyzed code is a conventional, non-malicious implementation of glob pattern expansion and directory traversal. It reads filesystem data based on user-provided patterns but does not exhibit data exfiltration, remote communications, or code execution risks within this fragment. Overall security risk is low, with standard OS-specific handling for nocase behavior. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/[email protected]` → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		Potential code anomaly (AI signal): npm `hardhat` is 75.0% likely to have a medium risk anomaly Notes: The code is a security-conscious utility for running a compiler subprocess and collecting its output. It uses temporary files and careful stream handling to avoid large buffers and ensure proper cleanup. No suspicious data leakage, hardcoded credentials, or backdoors are evident. The primary risk is the inherent risk of spawning external processes, but this is standard for compilers in build tools and is mitigated by controlled I/O and error handling. Confidence: 0.75 Severity: 0.55 From: packages/plugin-hardhat/package.json → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		Potential code anomaly (AI signal): npm `ignore` is 100.0% likely to have a medium risk anomaly Notes: The code fragment represents a conventional, well-structured path-ignore utility with caching and recursive parent-directory evaluation. Windows path normalization is present for compatibility but does not indicate malicious intent. No indicators of data leakage, external communication, or covert backdoors were found. Security impact primarily revolves around correct ignore semantics rather than intrinsic vulnerabilities. The component remains appropriate for use in a broader security-conscious pipeline if used with careful awareness of what is being ignored. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/[email protected]` → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		Potential code anomaly (AI signal): npm `tsx` is 100.0% likely to have a medium risk anomaly Notes: This fragment appears to be a bundler-generated bootstrap/initialization piece that imports many modules and executes an initialization function (r). No explicit malicious activity is evident within this fragment itself, but the risk stems from side effects of the imported modules on load. A careful review of the implementations of the imported modules (especially those exporting r and those performing initialization, build-time, or network/file operations) is recommended to rule out hidden telemetry, backdoors, or undesired side effects. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/[email protected]` → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		Potential code anomaly (AI signal): npm `undici` is 100.0% likely to have a medium risk anomaly Notes: The analyzed code appears to implement a standard in-memory cache batch operation flow (put/delete) with careful handling of response bodies by buffering and storing bytes for caching. No signs of malware, data exfiltration, backdoors, or obfuscated behavior were found. The primary security considerations relate to memory usage from buffering potentially large response bodies and ensuring robust validation within batch operations to prevent cache state corruption. Overall risk is moderate, driven by in-memory data handling rather than external communication. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/@nomicfoundation/[email protected]` → `npm/@nomicfoundation/[email protected]` → `npm/[email protected]` → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		Potential code anomaly (AI signal): npm `yargs-parser` is 100.0% likely to have a medium risk anomaly Notes: The analyzed code fragment represents a legitimate environment-variable integration path for a CLI argument parser (consistent with yargs-parser). There is no evidence of malicious behavior such as data exfiltration or backdoors. The primary security consideration is the potential for environment-driven overrides to affect runtime behavior; this is expected but should be carefully configured to avoid leaking sensitive settings. Overall risk is moderate but acceptable with proper configuration and validation. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/[email protected]` → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		Potential code anomaly (AI signal): npm `zod` is 100.0% likely to have a medium risk anomaly Notes: No explicit network exfiltration, reverse shell, or credential theft is present in this fragment. However, the code assembles and compiles arbitrary code via the Function constructor and invokes passed-in functions immediately (twice). That behavior constitutes a strong dangerous primitive (arbitrary code execution) which can be abused if any inputs (strings or args) are attacker-controlled. Treat this module as risky in threat models where inputs are not fully trusted; review call sites and sanitize/validate inputs or avoid dynamic evaluation. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/@nomicfoundation/[email protected]` → `npm/[email protected]` → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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

…SON files

…n with upgrades

…entation address tests

- Updated deploy and upgrade functions across multiple files to accept a NetworkConnection parameter.

…solidity, etherscan-api, and verify-proxy files

…for better context management

…ntract interactions. Also other fixes needed to make sure these would work.

… imports across test files

…tests, and add new test file for Upgrades library

…enhance test script for better argument handling

…ipt for better artifact management

…t handling in test script

…ration with dotenv support

…o artifacts for Hardhat 3 compatibility

…ompatibility

… hh tests, needing this commit to fix this.

…anges and usage examples

…erns I moved the contracts to a more suitable place for better usability. But this will force us to do at least a small change at the foundry repo.

socket-security · 2025-11-13T11:50:49Z

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

Package	Supply Chain Security	Quality	Maintenance	License
@openzeppelin/foundry-upgrades@0.4.0
@types/sinon@17.0.3 ⏵ 17.0.4	⁺¹	⁺¹
@types/node@20.19.21
hardhat@2.22.9 ⏵ 3.0.16	⁺⁵	^-8	⁺¹	⁺²⁰
ava@6.1.3 ⏵ 6.4.1	⁺¹
cbor@8.1.0 ⏵ 10.0.3	⁺¹
esmock@2.7.3
dotenv@16.6.1
rimraf@5.0.10
hardhat@2.22.9 ⏵ 2.26.3	⁺¹	⁺¹
@nomicfoundation/hardhat-verify@2.0.14 ⏵ 3.0.3	^-5	⁺¹	⁺¹
@nomicfoundation/hardhat-ethers@3.0.7 ⏵ 3.1.0	⁺¹	⁺¹	⁺²
@nomicfoundation/hardhat-ethers@3.0.7 ⏵ 4.0.2	⁺¹	⁺¹	⁺⁵
forge-std@1.9.7

View full report

…unction feat(tests): update tests to use GreeterInitializable for UUPS and Transparent proxies chore: update submodule for openzeppelin-foundry-upgrades

…ency

…config, to fix module import error.

…s, etc.

afa7789 added 5 commits October 16, 2025 00:32

chore(plugin): initial changes for hardhat 3

48b59e9

packages changes and initial config in accord to migration documentation.

chore(plugin): second change on tsconfig.json to be able to avoid tse…

37b710a

…rrors for ESM structure.

chore(dev): upgrading files to use hardhat3.

70993d7

importing errors + a few todos, change of Imports + new functions to use hardhat3 library in plugin files.

chore: lint fix

9d6d41e

chore(plugin): update imports to use .js extensions and adjust tsconf…

2516303

…ig for NodeNext module resolution

ericglau reviewed Oct 21, 2025

View reviewed changes

afa7789 added 4 commits October 21, 2025 20:15

chore(plugin): refactor plugin structure with hooks and update type e…

7fe4ec6

…xtensions for Hardhat compatibility ( still have to test it )

chore(plugin): refactor hooks to improve user config resolution and e…

bc0de37

…nhance artifact cleanup process

chore(plugin): enhance validation handling and namespaced storage lay…

13d2465

…out support in Solidity hooks

chore(plugin): update dependencies handling and enhance type extensio…

e579a89

…ns for defender integration

afa7789 added 19 commits October 22, 2025 17:31

chore(plugin): lint fixes.

6e4c825

chore(plugin): update import statements to use ES module syntax for J…

3fde741

…SON files

chore(plugin): update Hardhat configuration and fix plugin integratio…

0709925

…n with upgrades

chore(logs): debugging

71c16f8

chore(provider): adding one more log which should help.

f5266f5

chore(call): enhance logging for callOptionalSignature and add implem…

49726a7

…entation address tests

chore(test): migrate to ES module syntax and update upgrades import

fd2af91

feat: refactor deploy and upgrade functions to accept NetworkConnection

0a71170

- Updated deploy and upgrade functions across multiple files to accept a NetworkConnection parameter.

refactor(tests): migrate from CommonJS to ES modules in Hardhat tests

6858807

chore(tests): update imports and initialization in Hardhat tests

1a7e042

chore: clean up TODO comments and remove unnecessary code in deploy, …

78f3699

…solidity, etherscan-api, and verify-proxy files

feat: add warning for locked validations cache during compilation

db81b33

refactor(tests): replace proxyquire with esmock for module mocking

33f86a3

refactor(tests): replace network provider calls with ethers.provider …

0f67ffe

…for better context management

refactor(tests): replace hre.ethers with ethers for consistency in co…

fe45e60

…ntract interactions. Also other fixes needed to make sure these would work.

refactor(tests): migrate mockDeploy function to a new file and update…

c4f2a85

… imports across test files

feat(tests): enhance test script to separate Solidity and JavaScript …

acb0b57

…tests, and add new test file for Upgrades library

feat(tests): add WithConstructor and WithConstructorArray contracts, …

148f07a

…enhance test script for better argument handling

refactor(tests): improve build info file handling and update test scr…

524bf2e

…ipt for better artifact management

afa7789 added 7 commits November 6, 2025 12:14

refactor(tests): enhance logging in Upgrades test and improve argumen…

7b43183

…t handling in test script

feat(tests): add new contracts for testing and update hardhat configu…

af94560

…ration with dotenv support

feat(tests): update Solidity contracts for testing and inject AST int…

b8216fc

…o artifacts for Hardhat 3 compatibility

feat(tests): add GreeterInitializable contract and update tests for c…

35a4b68

…ompatibility

chore(tests): the changes regarding to solidity ended up breaking the…

011a216

… hh tests, needing this commit to fix this.

docs: add migration guide for Hardhat 2 to Hardhat 3 with breaking ch…

e3c8c30

…anges and usage examples

chore(contracts): Refactor and add new contracts for upgradeable patt…

96931d3

…erns I moved the contracts to a more suitable place for better usability. But this will force us to do at least a small change at the foundry repo.

afa7789 added 12 commits November 15, 2025 10:29

feat(contracts): add GreeterInitializable contract with initializer f…

3af64b8

…unction feat(tests): update tests to use GreeterInitializable for UUPS and Transparent proxies chore: update submodule for openzeppelin-foundry-upgrades

feat: add iginition modules and deployment.

5e984f8

chore(ux): ux improve on checking tests.

d6925d0

refactor: remove ignition cause it doesn't suit the plugin in itself.

689d581

feat: implement OZfilesToBuild utility for OpenZeppelin contract paths

881c3fb

feat: update upgrade paths in Greeter contracts and tests for consist…

66bb2e9

…ency

feat: update node version to 22.x in GitHub action setup

7cc1823

chore: yarn lint fix

cb998b4

chore(lint): fixed a bunch of lint issues.

16eaee4

chore(lint): more lint fixes

6899691

fix: update import paths and reorder dotenv configuration in hardhat …

c774103

…config, to fix module import error.

chore(fix): fixing tests that were broken due to contract name change…

e04b8a3

…s, etc.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Migration of hardhat-upgrade to plugin to use hardhat v3 #1194

Migration of hardhat-upgrade to plugin to use hardhat v3 #1194

Uh oh!

afa7789 commented Oct 20, 2025

Uh oh!

ericglau Oct 21, 2025

Uh oh!

afa7789 Oct 22, 2025

Uh oh!

socket-security bot commented Oct 22, 2025 •

edited

Loading

Uh oh!

socket-security bot commented Nov 13, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

		@@ -1,29 +1,37 @@
		/* eslint-disable @typescript-eslint/no-var-requires */
		// TODO figure out what is the newer, TASK_COMPILE_SOLIDITY and TASK_COMPILE_SOLIDITY_COMPILE

Migration of hardhat-upgrade to plugin to use hardhat v3 #1194

Are you sure you want to change the base?

Migration of hardhat-upgrade to plugin to use hardhat v3 #1194

Uh oh!

Conversation

afa7789 commented Oct 20, 2025

Uh oh!

ericglau Oct 21, 2025

Choose a reason for hiding this comment

Uh oh!

afa7789 Oct 22, 2025

Choose a reason for hiding this comment

Uh oh!

socket-security bot commented Oct 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security bot commented Nov 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

socket-security bot commented Oct 22, 2025 •

edited

Loading

socket-security bot commented Nov 13, 2025 •

edited

Loading