Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`rtk ruff check --statistics` prints ruff's statistics JSON instead of its table, larger than ruff's own output

Open Beginner friendly
#4,701 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@umi008 is already working on this.

Since Oct 21, 2026.

  • #4731 by @umi008 — open
  • #4732 by @umi008 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
cli, tooling

Research direction

Start by reading the ruff command handling and output filtering paths that inject --output-format=json and process check output; the issue does not name their files, so locate them from the rtk ruff entry point. Reproduce with rtk ruff check --statistics src and compare its output with ruff check --statistics src. Done means statistics output is compact and readable, with the command still returning the expected exit status.

Written by the indexing model from the issue text.

Description

area:cli bug good first issue priority:medium

rtk ruff injects --output-format=json into every check run where the user did not pick a format. With --statistics, ruff then prints statistics as JSON ([{"code","name","count","fixable","fixable_count"}]). That is not the diagnostics array filter_ruff_check_json expects, so the JSON comes back as-is: larger than ruff's table and in a different shape.

Reproduction (ruff 0.16.6, LC_ALL=C, 61 files with unused imports and unsorted import blocks):

command stdout
ruff check --statistics src 116 B: 242\tF401\t[*] unused-import, 60\tI001\t[*] unsorted-imports, totals
rtk ruff check --statistics src (develop 5ab629136) 248 B of pretty-printed JSON, exit 1

#3968 also routes the flag-first spelling rtk ruff --statistics to this path.

Direction: leave --output-format alone when --statistics is present (ruff's table is already compact), or summarise the statistics JSON.

Dominant language
Rust
Stars
85k
Forks
5.4k
Avg merge
5d 16h
Merged PRs (30d)
59

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rtk-ai/rtk

All issues in rtk-ai/rtk

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.