In addition to what Sinan said, we've had success running on fully untyped codebases. These are you some strategies that you can use to get results on untyped c

In addition to what Sinan said, we've had success running on fully untyped codebases. These are you some strategies that you can use to get results on untyped codebases: https://pyre-check.org/docs/pysa-coverage.html https://pyre-check.org/docs/pysa-coverage.html Types will definitely make Pysa find more issues, but you don't need 100% coverage, or really more than the minimal coverage described in that doc I linked, to start finding some issues.