crytic/slither

update register printer to consider multiple compilation units

Open

#1,780 opened on Mar 20, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (886 forks)batch import
buggood first issue

Repository metrics

Stars
 (4,769 stars)
PR merge metrics
 (Avg merge 54d 9h) (2 merged PRs in 30d)

Description

register_detector applies to each compilation unit https://github.com/crytic/slither/blob/776dcab44070b2d236ae3bcf3b92f4245f14037a/slither/slither.py#L181-L189 register_printer does not and needs to be updated https://github.com/crytic/slither/blob/776dcab44070b2d236ae3bcf3b92f4245f14037a/slither/slither.py#L201-L208

Contributor guide

Research direction
Study how `register detector` handles multiple compilation units in the linked code, then apply the same pattern to `register printer`.
Tech stack
python
Domain
securitytesting
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75