This integration is on a GitHub repository using the SonarSource/sonarqube-scan-action@v6 GitHub action.
I don’t know what the effect is on the scanning of not being able to parse the tsconfig.json but it seems to me that it is a false positive of javascript:S2260 is it possible to treat tsconfig.json as a JSONC file instead of pure json?
Thank you for the detailed report, including the example project, CI logs, and links to related discussions — that context is very helpful.
The issue SonarQube Cloud. is actually json:S2260 and not javascript:S2260. It is another analyzer (sonar-iac) that scans json files. It is know limitation of sonar-iac, because of the limitation of snakeyaml-engine used to parse JSON files.