Cairo-Mutate

• in-progress

Solderx

• SolderX is a developer-first, all-in-one Solidity flattener that handles files, folders, and verified contracts from various Explorers— all on-the-fly.
• It features robust import resolutions, advanced remapping support, SPDX unification, topological sorting, import deduplication & cyclic dependency detection.
• PyPI link : pypi.org/project/solderx/

Enhancement:#2998 (feat: Add RCN Mutator (require(...) Condition Negation)
This PR adds a new mutator: RCN (Require Condition Negation). RCN negates the first condition argument of require(...) calls. Examples:

• require(x > 0 && x < 10) -> require(!(x > 0 && x < 10))
• require(msg.sender == owner, "not owner") -> require(!(msg.sender == owner), "not owner")
• require(!isOwner, "owner-not-allowed") -> require(!(!isOwner), "owner-not-allowed")

Enhancement:#3000 (feat: Add ACN Mutator (assert(...) Condition Negation)
The mutator rewrites the first condition argument of assert(...) by wrapping it in a negation, so assertion-style guards can be flipped during mutation testing. Examples:

• assert(x > 0 && x < 10) becomes assert(!(x > 0 && x < 10))
• assert(msg.sender == owner) becomes assert(!(msg.sender == owner))
• assert(!isOwner) becomes assert(!(!isOwner))

Enhancement:#2867 (feat: Add detector for msg.value usage unreachable from payable entry points)
This PR resolves introduces a new Slither detector, msg-value-in-nonpayable, which identifies uses of msg.value in functions that can never be reached from any payable public or external entry point.
In such cases, msg.value is provably meaningless:

• it is always zero, or
• execution always reverts . This detector helps developers catch logic errors, dead code, and incorrect assumptions about ETH flow early.

Enhancement:#2753
(feat: Add Function module to detect functions returning msg.sender directly or via alias)
This PR introduces a new method is_returning_msg_sender() in the Function class, enabling detection of Solidity functions that return msg.sender, either directly or through transitive variable aliasing.

• The newly added method Function.is_returning_msg_sender() returns True if:
  • The function directly returns msg.sender ,
  • The function returns a variable that was directly or transitively assigned from msg.sender

Fix Bug:#2747
Updates the logic in get_msg_sender_checks(), removing duplicates & repeated msg.sender condition nodes

Enhancement:#1722
Adds function that would be helpful to de-register a detector class from the list of detectors already registered with the slither object

Enhancement:#1724
Adds a function that Un-Register a printer class from the list of printers already registered with the slither object.

Fix Typos : #1705 , #2751 ( Fix typo's )

• #1705 - misspelt msg.sender in the reentrancy-eth module
• #2751 - misspelt terms in function doc-strings

Enhancement:#1201 : Fix test run inconsistencies and output mismatches in (ch10_01)

• Fixes inconsistencies in test cases sections of assert!, assert_eq!, assert_ne!, #[should_panic], #[ignore] Macros and section of : Running Single Tests
• Adds missing testcases in the contracts and fixes output logs as expected behaviour

Enhancement:#1193

• Adds note on multiple derivable traits on structs

Enhancement:#1191 : Tuple Matching Only Supports Enums (ch06-04)

• Issue: The "Matching Tuples" section implies that all tuple types can be used in match, but tuples with primitive types like (u8, u8) cause a compile-time error.

• Fix: Add a note/text clarification that tuple matching currently supports only enums.

Issue #1192
Rephrase generics example sentence for clarity

Issue #1190
Fix incorrect usage of function names in quiz.