# Old code smells reported as "new code" **URL:** \ **Category:** SonarQube Server / Community Build\ **Tags:** coverage\ **Created:** [December 5, 2023, 7:16pm UTC](https://community.sonarsource.com/t/old-code-smells-reported-as-new-code/105535 "2023-12-05T19:16:58Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [December 13, 2023, 1:09pm UTC](https://community.sonarsource.com/t/old-code-smells-reported-as-new-code/105535/4 "2023-12-13T13:09:00Z")
Hi, From your followup, I think I see two things going on. > [@nk-ot](#): > > Tough to characterize the new code smells—there are over 400 new ones. I see many smells that are marked as “rule deprecated” although probably only 100 or so. Let’s talk about what’s in the new code. Did something in your code get marked deprecated? Did maybe a library get upgraded (and the new version includes new deprecations)? That would legitimately cause old uses of that newly deprecated code to have “new” deprecation issues raised on them. There’s a little more in [this guide](https://community.sonarsource.com/t/understanding-new-issues-on-old-code/96606) > [@nk-ot](#): > > We had one analysis that had over 1000 code smells before it fell down to 586 on a subsequent analysis. We get occasional reports of this (and we’ve seen it occasionally ourselves), but it’s as hard to track down as bigfoot. If you spot any pattern at all here, we’d love to have the details. > [@nk-ot](#): > > I see a notice that appears new: “The quality gate used by this project does not comply with Clean as You Code.” Yeah… that’s been toned down in subsequent versions. Sorry 'bout that.   Ann --- _[View the full topic](https://community.sonarsource.com/t/old-code-smells-reported-as-new-code/105535)._