repository·master·Indexed 11 days ago
https://github.com/foundry-rs/foundryA portable and modular toolkit for Ethereum application development written in Rust, providing tools for building, testing, and interacting with smart contracts.
Foundry is a modular toolkit for Ethereum development consisting of four primary tools:
foundry-common crate provides a collection of shared utilities designed to assist in the development and operation of various Foundry tools. It serves as a foundational layer for building and using the broader Foundry ecosystem.Tempo Foundry is a high-performance, portable, and modular toolkit for Ethereum application development written in Rust. It primarily consists of two core tools:
Foundry is a high-performance, modular toolkit for Ethereum application development written in Rust. It consists of four primary tools:
The arbitrary-send-erc20-permit lint rule (Severity: High) detects a dangerous pattern where a contract calls permit on a token and subsequently calls transferFrom using an arbitrary from address that is not proven to be msg.sender or address(this).
This pattern is dangerous when used with tokens that do not actually implement permit but have a fallback function (e.g., WETH). In such cases, the permit call might silently succeed without actually granting an allowance. If the subsequent transferFrom uses an attacker-supplied from address, the contract might inadvertently drain funds from a user who had previously granted an allowance to the contract, because the contract incorrectly assumes the permit call authorized the transfer.
The inline-assembly lint (Severity: Info, ID: inline-assembly) flags every assembly { ... } block in your Solidity code. Because inline assembly bypasses Solidity's safety features (type checks, overflow checks, and memory layout invariants), it is a common source of high-impact bugs.
This lint reports all assembly blocks, including those using the "evmasm" dialect or the ("memory-safe") flag. For blocks marked as memory-safe, the lint provides a softer message acknowledging the developer's attestation, shifting the review focus from memory layout to business logic and side effects.
The write-after-write lint rule (Severity: Gas, ID: write-after-write) identifies instances where a state variable is written to consecutively without the first value ever being read. The first write is considered dead code because it incurs an SSTORE gas cost but its value is immediately discarded by the subsequent write.
= assignments.delete operations on bare state variable identifiers.(x, y) = (1, 2)), where each component is tracked individually.++x, x--), as the write they produce can be immediately overwritten.+=, |=).mapping[k], struct.field).&&, ||, or ternary operators are handled conservatively to prevent false positives across short-circuit paths.The rtlo lint rule flags the presence of Unicode bidirectional override characters in source code. These characters (such as the right-to-left override codepoint U+202E) can be used to create "Trojan Source" attacks, where code is rendered visually in a different order than how the compiler actually reads it. This allows malicious behavior to be hidden during visual code reviews.
This rule detects these characters when they are embedded in:
Severity: High
ID: rtlo
evm-networks crate provides a mechanism for defining and sharing custom network features across Foundry's core tools, including anvil, forge, and cast. Currently, this system is used to implement custom precompiles, with future support planned for custom transaction types. Custom network features can be toggled via CLI flags, configuration in foundry.toml, or automatically enabled based on the detected chain_id.The formatter preserves developer intent by categorizing comments into Isolated, Mixed, or Trailing types.
BlankLine comments. The formatter preserves vertical spacing between logical blocks but collapses multiple consecutive blank lines into a single blank line to maintain a clean rhythm.Break tokens around comments to ensure correct spacing. For blank lines, it emits one or two hardbreaks to maintain the original vertical rhythm.