crytic / crytic/rattle

Static security checkers

Open
#10 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
365
Forks
41
PR merge metrics
No merged PRs in 30d

Description

Identify which security checkers apply from slither and port them to rattle

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the existing Rattle code and Slither's security checkers to identify the applicable checker set. The issue names no files, tests, or entry points, so first determine where analyses are implemented and how they are validated. Done means the selected Slither checkers are ported to Rattle with corresponding validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
reverse-engineering, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.