Hey @pablo-olmedo-poex,
Currently, our analyzer fails when TSconfig files have references such as extends to TSconfig files that it cannot access such as the ones located in dependencies. For autoscan, this is an issue because we do not download the dependencies before running the analysis.
To fix this issue, we recommend bringing the compiler options in the referenced TSconfig file into the one that is part of your project and removing any extends property pointing to TSconfig files in dependencies.
An alternative is using the scan in CI/CD where node_modules can be installed before the analysis.