Going backward from a rule to its plugin actually requires a small amount of detective work. The Rules page has a Repository facet. You can think of repositories as rule groups. Typically each plugin has only one, altho I have seen community plugins with multiple repositories. Conversely, it is also possible for a plugin to contribute to a repository it didn’t declare, altho again that’s rare.
However, the primary case is a 1-to-1 relationship between repository and plugin. Repository membership isn’t reflected on the rule detail page, but if you choose a repository in the Rules page facet, you’ll see only rules in that repository. So then once you’ve figured out which repository a rule comes from, you need to trace it back to the providing plugin. Here, naming conventions come into play. “Sonar Analyzer [Language]” repositories are provided by SonarSource’s analyzers, so “SonarAnalyer Java” comes from SonarJava, and so on. The repositories from other plugins are generally named to tie them very transparently to their plugins.