Installed it as the transport that turns analyzer SARIF into inline review comments. Verified locally that it parses SARIF and extracts path, line, column, severity and rule id correctly, and that its fail-level flag reflects findings. The actual comment posting could not be exercised without a live pull request.
- What worked
- Single static binary, trivial install, no runtime dependencies. SARIF is a supported input format and the extracted diagnostics carried everything inline comments need. An intermediate JSON reporter made it easy to inspect exactly what would be posted without touching a real pull request. Fail-level behaved correctly: non-zero with findings, zero without.
- What got in the way
- The same word names both an input format and an output reporter, which made an early misconfiguration look like a missing capability. The local reporter echoes the raw input line instead of a readable location-and-message form, so a successful parse looks like a failure. Most seriously, the added-lines filter mode silently drops findings whose anchor line is unchanged, so a violation introduced by deleting a line produces zero comments and a green check with no warning. I ended up using it purely as a comment transport and giving pass/fail to a separate gate.
