psf / black

GitHub metadata describes this repository as "The uncompromising Python code formatter", and lists a documentation homepage at https://black.readthedocs.io/en/stable/. Its topic tags include python, formatter, codeformatter, and pre-commit-hook. Platform metadata reports Python as the primary language, with 5,440,093 Python bytes in the recorded language breakdown. The analysis processed 482 files and names action/main.py as a detected starting point. The recorded license is MIT. Counters recorded 41,844 stars (as of 2026-09-14) and a latest release 26.5.1 published 2026-05-18. The description and homepage are author-claimed values from the GitHub API; the topic, language, license, star, and release fields are observed platform records.

The analyzer flags action/main.py as a likely executable entrypoint based on a filename heuristic. Bounded execution paths traced from it reach os.getenv and Path and then stop at unresolved external boundaries, so the statically visible flow from that file is shallow. The main packages carry their own __main__ guards:

• src/black/__init__.py ends with if __name__ == "__main__": patched_main()
• src/blackd/__init__.py uses the same patched_main() pattern
• src/blib2to3/pgen2/driver.py exits through sys.exit(int(not main())) under its guard
• scripts/generate_schema.py calls main(); scripts/release.py calls sys.exit(main())

In total the analysis records 18 entrypoints and 176 bounded execution paths.

Four top-level directories are flagged as likely subsystems: docs, scripts, src, and tests. The recorded relation graph holds 9,339 edges — 8,219 calls and 1,120 imports — of which 8,487 are external or unresolved and 852 resolve locally. Role candidates are computed from statically resolved call degree:

• src/black/linegen.py (79 incoming / 79 outgoing) and src/black/trans.py (66 / 66) are service/core candidates, consistent with hub-like formatting logic.
• tests/util.py shows the highest incoming degree among listed roles (118 in / 18 out); tests/test_black.py shows the highest outgoing degree (104 in / 177 out).
• src/black/__init__.py is an entry/orchestration candidate (42 / 42); comments.py, nodes.py, and files.py are moderate-degree service/core candidates.

Because most relations are unresolved, these degrees describe only the resolved local subset.

The repository contains 7 build/dependency manifest files. Dependency parsing in this analysis reads only requirements-style manifests and skips pyproject.toml dependency tables, so this packet itemizes no concrete dependency records. The tests directory supplies 326 test-like files.

On the test surface:

• tests/test_black.py defines BlackTestCase (lines 171-2283) plus the TestCaching, TestFileCollection, TestDeFactoAPI, and TestASTSafety classes.
• tests/util.py defines shared helpers: assert_format, all_data_cases, and read_data.
• scripts/fuzz.py runs test_idempotent_any_syntactically_valid_python under its __main__ guard, and its comments describe optional coverage-guided fuzzing when Atheris is available.

1. README.md and pyproject.toml — the analyzer classifies both as project-level important files. Treat README-derived statements as author claims, since extraction is line-based.
2. LICENSE — the recorded license is MIT.
3. src/black/__init__.py — read main() (lines 554-776), then get_sources() (779-874) and reformat_code() (877-904).
4. src/black/linegen.py — LineGenerator (110-735) and transform_line (750-885) live here; by call degree this is a core candidate. So is src/black/trans.py.
5. action/main.py — the analyzer's flagged starting entrypoint, so it is a reasonable first stop.

• 8,487 of the 9,339 recorded static relations are external or unresolved.
• Reflection, runtime dependency injection, dynamic imports, monkey-patching, generated code, framework runtime wiring, and dynamic dispatch are not resolved, so plugin-style loading through such mechanisms is not traced by this analysis.
• Install, run, and build inference is partial, and installation commands are unconfirmed.
• Dependency parsing covered only requirements-style manifests, so the declared dependency set is not itemized here.
• Every bounded execution path in the packet that starts at action/main.py terminates with reason unresolved_boundary; none was executed.
• The manifest's capability fields describe the analyzer itself, not the analyzed repository, and are excluded from repository evidence.
• The packet's directory listing includes a top-level plugin directory, but nothing in the packet establishes how it is discovered or loaded; this stays unresolved.