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!
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!