Okay! Now I think I understand. I guess you have the same total number of issues, but some are classified differently.
What you’re seeing is an artifact of the evolution of our thinking/understanding on these rules. Some rules start life as one type (e.g. Bug) but then get reconsidered and reclassified (Code Smell). The issues that were raised when the rule was a Bug rule were raised as Bugs. Issues raised after the change are raised as Code Smells. The old Bug issues don’t (currently! - there’s been internal discussion about this lately) get reclassified with the rule. Why not? Because suddenly “upgrading” old Code Smells to Bugs or vice versa could have significant impacts on folks Quality Gate statuses and so far we’ve always chickened out of that.
This shouldn’t be the case if both instances are the same version & running the same versions of the analyzer. But yes, since this sort of thing can change from version to version if the details don’t line up correctly then you could see this sort of difference.