Master

[Dargon789]

Description

Concise description of proposed changes

Additional Information

• I read the contributing docs (if this is your first contribution)

Your ENS/address:

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
my-vue-app-react	Ready	Preview, Comment	Jun 17, 2026 10:04am
template-ethereum-contracts	Ready	Preview, Comment	Jun 17, 2026 10:04am
template-ethereum-contracts-vue	Ready	Preview, Comment	Jun 17, 2026 10:04am

[sourcery-ai]

Sorry @Dargon789, your pull request is larger than the review limit of 150000 diff characters

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive Ethereum development environment, incorporating Foundry and Hardhat configurations, Solidity contracts for registries and tokens, and utility scripts for network management. Critical feedback identifies a malformed Dockerfile with conflicting image definitions, invalid dependency versions in package.json, and security vulnerabilities and logic errors in the custom script runner. Additional recommendations focus on code cleanliness, such as removing unused imports, eliminating redundant test logic, and adopting best practices for integer parsing and file formatting.

I am having trouble creating individual review comments. Click here to see my feedback.

Dockerfile (1-40)

This Dockerfile appears to contain definitions for two separate images (one for Node.js, one for Python) concatenated together. A single Dockerfile can only define one image unless it's a correctly structured multi-stage build. The second FROM instruction on line 22 will cause build errors.

If you intend to define two separate services, they should be in two separate Dockerfiles (e.g., Dockerfile.node and Dockerfile.python).

contracts/package.json (18-53)

The versions specified for @types/node (^25.6.2 on line 33) and typescript (^6.0.3 on line 49) are incorrect. The latest major versions for these packages are 20 and 5, respectively. These invalid version numbers will cause dependency installation to fail. Please correct them to valid, existing versions.

_scripts.js (76-163)

The execute function constructs and runs shell commands using shell: true, which is dangerous as it can lead to command injection vulnerabilities if any of the inputs (fixedArgs, filepath, extra) are not properly sanitized. A malicious argument could allow for arbitrary command execution.

It is highly recommended to refactor this to avoid shell: true. Instead, pass the command and its arguments as an array to spawn or execFile.

_scripts.js (51-62)

There is a syntax error in the execute function. The spawn(...) call is not correctly placed within the promise executor, which will cause the script to fail at parse time. It should be moved inside the new Promise(...) callback.

Additionally, when using shell: true, the second argument to spawn (the array of arguments) is ignored, so it can be removed for clarity.

	return new Promise((resolve, reject) => {
		const onExit = (error) => {
			if (error) {
				return reject(error);
			}
			resolve();
		};
		spawn(command, {
			stdio: 'inherit',
			shell: true,
		}).on('exit', onExit);
	});

hello_foundry/.gas-snapshot (2)

This file is missing a newline character at the end. It's a common convention and good practice to end files with a newline.

CounterTest:test_Increment() (gas: 31851)

Counter/test/Counter.t.sol (4)

The console import is not used in this test contract. It should be removed to keep the code clean.

import {Test} from "forge-std/Test.sol";

Counter/script/Counter.s.sol (4)

The console import is not used in this contract. It should be removed to keep the code clean and avoid confusion.

import {Script} from "forge-std/Script.sol";

Counter/.gas-snapshot (2)

This file is missing a newline character at the end. It's a common convention and good practice to end files with a newline.

CounterTest:test_Increment() (gas: 31851)

hello_foundry/script/Counter.s.sol (4)

The console import is not used in this contract. It should be removed to keep the code clean and avoid confusion.

import {Script} from "forge-std/Script.sol";

hello_foundry/test/Counter.t.sol (4)

The console import is not used in this test contract. It should be removed to keep the code clean.

import {Test} from "forge-std/Test.sol";

script/Counter.s.sol (4)

The console import is not used in this contract. It should be removed to keep the code clean and avoid confusion.

import {Script} from "forge-std/Script.sol";

test/Counter.t.sol (4)

The console import is not used in this test contract. It should be removed to keep the code clean.

import {Test} from "forge-std/Test.sol";

test/SimpleERC20.test.ts (28)

This transfer call is redundant because the subsequent expect on line 30 also performs a transfer while checking for the event. You can remove this line to make the test cleaner and more focused on a single action.

utils/network.ts (82)

It's a good practice to always specify the radix when using parseInt to avoid unexpected behavior with strings that could be interpreted as octal or hexadecimal. Please add the radix 10.

								? parseInt(process.env.HARDHAT_FORK_NUMBER, 10)

utils/network.ts (89)

It's a good practice to always specify the radix when using parseInt to avoid unexpected behavior. Please add the radix 10 to this parseInt call.

							interval: process.env.MINING_INTERVAL.split(',').map((v) => parseInt(v, 10)) as [