crytic / crytic/slither

Slither doesn't resolve references across compilation units

Open
#2,102 7 comments 0 reactions 0 assignees View on GitHub
documentation question
Dominant language
Python
Stars
6.4k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

As discussed on [telegram](https://t.me/ETHSecurity/79291), it seems to me that Slither does not resolve references across compilation units. Here is a reproduction repo: https://github.com/hacker-DOM/reference-resolving. The tldr is multiple `Contract` instances will exist in `Slither.contracts` for each contract that spans multiple compilation units, and so a regular usage of the Api like finding a contract with a given name (if there's just one in my codebase) and looking for its derived contracts will report inaccurate results.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.