Hey @dlecan
Sorry this thread fell off my radar!
Yes, switching to CI-based analysis where the tsconfig.json files are available (because you’ve run npm install or whatever you use to grab this module containing the tsconfig.json file before analysis) would fix the issue.
You could also try having the tsconfig.json file available in your repo so it’s picked up by automatic analysis, but I’m guessing that’s not ideal.
Long-term, we may allow analysis without the tsconfig of the project (although not necessarily targeted for this use-case)
I think it’s an interesting situation. I’ll ping the right team internally for awareness of this scenario.