/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

psf/black

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T16:09:00.759Z

1mo ago

psf/black

psf/black is the official Python code formatter project: a stable, widely used tool with 41k+ stars and 2.7k+ forks, focused on deterministic formatting and minimal diffs. The repo is actively maintained, with recent commits on 2026-03-30 and documentation, testing, packaging, Docker, and GitHub Actions support in the tree.

Loading tags...

Stars41,433

Forks2,745

Default branchmain

Last pushed2026-03-30T02:10:08Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose Pyink if you want Black’s ecosystem but need its fork-specific formatting tweaks; stay with upstream Black if you want the newest formatter fixes, syntax support, and lowest maintenance risk.

Choose this fork if tab indentation is a hard requirement and you want to stay close to Black’s behavior. Prefer upstream Black if you value active maintenance, latest syntax support, and lower adoption risk.

Choose this fork only if you need its retained local formatting behavior; otherwise upstream Black is the safer default because it is much newer and better maintained.

Choose this fork only if your goal is Vim-specific Black integration and you can tolerate an old, largely frozen codebase. If you need current Black behavior, active maintenance, or broader tooling support, upstream Black is the safer choice.

Prefer upstream `psf/black` unless you need this exact historical snapshot. This fork does not add user-visible value and is behind current upstream maintenance.

Prefer this fork only if you need its specific downstream behavior or integrations. For most users, upstream Black is the safer choice because this fork is stale and materially behind current maintenance.

Prefer this fork only if single-quote formatting is a hard requirement and you are comfortable owning a stale, highly divergent formatter. For most adopters, upstream Black is the safer choice.

Choose this fork only if tab-based formatting is the requirement. For anyone wanting a maintained, current formatter, upstream Black is the better default.

Prefer upstream Black unless you specifically need this fork's legacy or custom formatter behavior. This fork is materially outdated and diverges enough that adopters should expect compatibility and maintenance risk.

Prefer upstream psf/black unless you specifically need an old, custom 2020-era fork and are prepared to maintain it yourself; this fork is not a healthy default adoption target.

Fork comparison

google/pyink

70/100

active

significant_divergence

Choose Pyink if you want Black’s ecosystem but need its fork-specific formatting tweaks; stay with upstream Black if you want the newest formatter fixes, syntax support, and lowest maintenance risk.

Likely purpose

A formatter fork for teams that want Black-compatible tooling but prefer Pyink-specific formatting rules and a couple of extra configuration behaviors.

Best for

Teams already on Black who want a mostly compatible fork with a few local style exceptions.; Projects that format notebooks and need Pyink-specific Unicode handling.; Maintainers willing to accept upstream lag in exchange for customized formatter behavior.

Additional features

Prevents blank lines from being inserted between docstrings and the next class or function when formatting only a line range.
Adds a `--pyink-ipynb-unicode-escape` option for controlling Unicode escaping in Jupyter notebook formatting.
Carries fork-specific formatting behavior changes rather than staying byte-for-byte aligned with upstream Black.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

It lags upstream Black by 200 commits, so recent Black fixes and syntax support are not yet included in this fork.
Upstream changes from late March 2026, including new formatter support and maintenance updates, are missing until Pyink rebases again.
A temporary `pathspec<1.0.0` restriction suggests dependency flexibility may be narrower than upstream.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Lets adopters keep most of Black’s formatter ecosystem while choosing slightly different formatting rules.
Recent Pyink commits show continued maintenance and active rebase work.
Useful for notebook-heavy or line-range-formatting workflows that want different output from upstream Black.

Risks

Materially behind upstream, so adopters can miss recent bug fixes and Python syntax support.
The large diff and many deleted upstream files indicate stronger divergence, which increases merge and maintenance cost.
Behavioral differences may surprise teams expecting exact Black output.