DavidKorczynski

> employ call_depth to avoid discrepancies like the one reported, i.e. if the next function in the list is not a callee (an incremented call_depth), do not proceed to detect...

> There are a number of things that can be refine in the existing definition and many of which are not super big. See here for reference #254 I held...

I think it would be ideal if the branch blockers capture that if-statement. It will clear up a lot of easy-to-misunderstand scenarios if a blocker is identified as a specific...

instead of adding a server we may be able to push some logic into javascript

perhaps related: https://github.com/ossf/fuzz-introspector/issues/111

Good ideas! > 3\. Calls other functions in the same library (indicates close to the root call) fyi in the functions overview tables we have the columns "Functions reached" and...

sounds good

Thanks, much appreciated! I will get something like this up. In short, there are real world example projects in the [examples](https://github.com/ossf/fuzz-introspector/tree/main/examples) folder. I will create some documentation that clarifies the...

Yeah makes sense, I have this in mind for the near future but will just add one or two things in the compiler plugin to make the UX a bit...

Setting this to higher priority since we need to provide better guards for OSS-Fuzz bumps: https://github.com/google/oss-fuzz/issues/7635