crytic/slither

Identify missed reentrancy exploits by Slither

Open

#1,840 opened on Apr 14, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (886 forks)batch import
enhancementhelp wanted

Repository metrics

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

Description

Describe the desired feature

Identify which reentrancy exploits in my collection repo are currently overlooked by Slither and report them individually. Based on these findings, the reentrancy detectors can be (hopefully) improved.

Contributor guide

Research direction
Review the collection of reentrancy exploits and run Slither on each to identify which are not detected. Document each missed exploit and consider improvements to Slither's reentrancy detectors.
Tech stack
python
Domain
securityblockchain
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
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
SoliditySlither
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40