SonarCloud shows zero issues for new code (last 30 days)

  • ALM used: GitHub
  • CI system used: GithubActions
  • Scanner command used: SonarSource/sonarcloud-github-action@master
  • Languages of the repository: Typescript / NestJS


I’ve just setup SonarCloud on a private Typescript/NestJS repository, and it seems to be working fine for pull requests as it’s able to catch issues and analyze code coverage on every PR, it even shows me the repository information for the main branch. However, there is something very odd, for the new code status (last 30 days) it shows 0 issues and no code coverage or code duplication.

At first, I thought that it had to do with code not being modified in the last 30 days, but there were source code changes in that time period.

Weirdly enough, a lot of these source files that changed recently, do have issues on the overall report.

What could be the problem?


Hi @BernalCarlos,

Welcome to the community, and really sorry for the delayed response!

Indeed, at a glance, this looks a bit strange. To understand better, we need a bit more data. For example, from the screenshot of the GitHub repo, we cannot tell if the recently changed files were actually part of the analysis.

Let’s try to narrow down. Please find a file such that:

  • the file was changed within the last 30 days
  • the file is part of the analysis: you can see it on the Code tab of the project on SonarCloud
  • the lines that changed contain at least one issue
  • the lines that changed have some test coverage

When you find a suitable file, note that the Code tab shows a green border at the left when the line is covered by tests. And the issue shows the date when it was created.

Please let us know what you find, and then we can dig further. If you prefer to share these details privately, we can open a private thread from here, just let us know!