Gets the short identifier of the detector, used in analyzer warnings.
The unique identifier of the detector.
Gets the kind of the detector.
Defines the behavior of warnings generated by this detector when working with multiple projects within a single Tact configuration.
Here are the available options:
"union"
Leave this value if you don't care about warnings generated in other projects."intersect"
If the warning is generated for some source location of the imported file,
it should be generated by each of the projects. Example: Constants from an
imported file should not be reported iff they are unused in all the projects,
so you need "intersect".Checks whether this detector needs the Soufflé binary to be executed.
Executes the detector's logic to check for issues within the provided compilation unit.
The compilation unit to be analyzed.
List of warnings has highlighted by this detector.
Protected
makeA wrapper method that creates Misti warnings with additional context about the detector generated it.
Protected
skip
A detector that identifies uses of the zero address.
Why is it bad?
Using the zero address in smart contracts is typically problematic because it can be exploited as a default or uninitialized address, leading to unintended transfers and security vulnerabilities. Additionally, operations involving the zero address can result in loss of funds or tokens, as there is no private key to access this address.
Example
Use instead: