New possible rules to analyze

[dbale-altoros]

boolean_comparison
Checks if an expression contains a comparison with a boolean literal, which is unnecessary.
(best practices)

division_before_multiplication
Checks for division operations before multiplications, which can result in value truncation.

external_call_in_loop
Checks if any functions contain any loops which perform calls to external functions.
(security)

missing_logs
Checks for publicly-accessible functions that make changes to storage variables without emitting logs.
(security)

storage_read_in_loop_condition
Checks for loops that contain a storage read in their condition, which can increase gas costs for each iteration.
(gas)

contract-name-as-type
Prevent the use of contracts as types in variable declarations
IERC20 public token instead of ERC20 public token
(force the use interfaces names as types)

avoid-magic-addresses
Use immutable variables or registry instead of hardcoding addresses
(avoid magic addresses)

move-to-interface
Move events and enums to interfaces as good practices
(best practices)

[ScreamingHawk]

unused_return_value

This is already a compiler warning for low level calls and could be extended for all calls.

[dbale-altoros]

@ScreamingHawk thanks for your input

[0xcompose]

Would love to see missing_logs rule!