Hi all,
I’ve been running SonarQube Community Build on a few projects and kept hitting the same friction: when I wanted to triage issues, pull them into scripts, or feed them into an AI coding assistant, I either had to click through the web UI or hand-roll curl calls against the Web API.
I built sonacli to scratch that itch — a small Go CLI that wraps the parts of the Web API I reach for most often, with both pretty terminal output and JSON output for scripting.
A few things it can do today:
sonacli auth setup --server-url http://127.0.0.1:9000 --token <token>
sonacli project list --pretty
sonacli issue list <project-key> --pretty
sonacli issue show AX1234567890 --pretty
# Also works with full issue URLs pasted from the browser:
sonacli issue show 'https://sonarqube.example.com/project/issues?id=my-project&issues=AX1234567890'
Scope up front so nobody is surprised:
- Targets SonarQube Community Build
v25.x+only (that’s what I run). - Linux and macOS only for now.
- Complementary to SonarLint, the scanners, and the web UI — it’s a thin read client for analysis results, not a replacement for any of those.
- Open source, MIT.
Repo: GitHub - mshddev/sonacli: CLI for consuming SonarQube analysis reports · GitHub
I would love feedback from people who are using Community Build day-to-day:
- Which endpoints or filters do you reach for that aren’t there yet?
- Is the JSON shape useful for your CI/automation workflows?
- How do you prefer to install tools like this (tarball, Homebrew, apt,
go install)?
Not asking for stars — just trying to learn where this is useful and where it isn’t. Thanks!
