registry: add SonarQube CLI (aqua:SonarSource/sonarqube-cli)

[3PeatVR]

Summary

Adding SonarQube CLI to mise using aqua

Popularity

• GIthub (SonarSource/sonarqube-cli): 140 stars, 5 forks, last release 0.12.0.1512 on 2026-05-11
• Aqua registry: already tracked (pkgs/SonarSource/sonarqube-cli/pkg.yaml)
• CLI for SonarQube, one of the most used static analysis tool

[gemini-code-assist]

Code Review

This pull request introduces a new registry configuration for the SonarQube CLI. The feedback suggests improving the file's consistency by using 2-space indentation and adding a trailing comma in the backends array. Additionally, the reviewer recommended simplifying the version matching logic in the test command and including the expected 'sonar version' prefix to ensure more robust testing.

[greptile-apps]

Greptile Summary

This PR registers the SonarQube CLI (sonar) as a new mise tool backed by aqua:SonarSource/sonarqube-cli.

• The single TOML entry is structurally correct: it uses the preferred aqua: backend tier and includes a well-formed test command with a template that correctly trims the 4-part aqua version tag (0.12.0.1512) down to the 3-part string the CLI reports (0.12.0).
• The adoption threshold documented in CLAUDE.md ("GitHub stars in the thousands, not hundreds") is not met by the numbers in the PR description (140 stars / 5 forks), and the tool is currently in Beta according to SonarSource's own docs — concerns that have already been raised in earlier review threads.

Confidence Score: 4/5

The TOML file itself is mechanically correct and safe to merge from a technical standpoint; the open question is whether the tool meets the registry's popularity bar.

The change is a single, well-formed registry entry with no logic errors. The only risk lies in whether the maintainer will accept it given the tool's current adoption numbers and Beta status — not in the code itself.

registry/sonarqube-cli.toml — maintainer acceptance depends on the tool's popularity, not on anything in the file's content.

Important Files Changed

Filename	Overview
registry/sonarqube-cli.toml	New registry entry for sonarqube-cli using the preferred aqua backend; structurally well-formed with a correct version-slicing template for the 4-part aqua tag vs 3-part CLI output

_{Reviews (5): Last reviewed commit: "registry: add SonarQube CLI (aqua:SonarS..." | Re-trigger Greptile}

[risu729]

Why do they have .1512 or like that?

$ mise ls-remote aqua:SonarSource/sonarqube-cli
0.5.0.409
0.6.0.579
0.6.1.603
0.7.0.711
0.8.0.783
0.8.1.798
0.9.0.977
0.10.0.1266
0.11.0.1439
0.12.0.1512

[3PeatVR]

@risu729 This represents the build number, and more precisely it increments everytime the CI pipeline runs. This can help finding the number of the CI run in which the release was built 👍 , like "This artifact was built in CI #1512" for instance. Since it is not useful for the user, I guess that is why they do not display it when you do sonar --version.

[risu729]

I see, that's fair.