trailofbits / trailofbits/trailmark
[FEAT] state web across smart-contract languages
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 487
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
I'm currently building a small side project integrating with Trailmark, which requires a 'state-web' , i.e. READS/WRITES edges for persistent state (which functions read/write which contract storage) alongside the existing calls/inherits graph. My first instinct was doing it by layering semgrep or similar on top, but looking closer at the Trailmark code it feels like natural to add it as a feature.. If this aligns with your projects vision I would author a PR keeping true to syntactic-only, compile free analysis. Let me know!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points, so start by locating Trailmark's existing calls/inherits graph analysis and its language parsers. Done would mean a syntactic-only, compile-free state-web feature that adds READS/WRITES persistent-state edges across smart-contract languages alongside the existing graph.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- blockchain, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100