# Install darker with Homebrew

Apply Black formatting only in regions changed since last commit. Version 3.0.0 via Homebrew; verified 2026-07-13.

## Install

```sh
sudo av install brew:darker
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install darker
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:darker
- **Package manager:** Homebrew
- **Version:** 3.0.0
- **Source summary:** Apply Black formatting only in regions changed since last commit
- **Homepage:** <https://github.com/akaihola/darker>
- **Last updated:** 2026-07-13T14:12:41Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- darker (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 3.0.0
## Project history and usage

Darker is a Python formatting tool that applies Black-style formatting only to regions changed between Git revisions or in a working tree.

### Project history

The README explains Darker as a response to a common adoption problem for Black: teams often want consistent formatting without one large repository-wide reformat. Darker compares revisions, formats with Black or another supported formatter, and writes back only the changed regions.

### Adoption history

Darker's official docs document installation from PyPI, conda-forge availability, editor integrations, pre-commit usage, and a GitHub Action. The changelog records early 2020 releases, a 1.0.0 release in July 2020, conda-forge availability in 1.2.2, support for plain directories in 1.4.0, and a 3.0.0 release that added Ruff formatter support while moving linting to Graylint.

### How it is used

Users typically run darker on files or directories inside a Git repository, optionally selecting a revision range, showing a diff, or configuring behavior through pyproject.toml under tool.darker.

### Why package nerds care

Darker matters to Python package maintainers because it is about incremental formatter adoption: it reduces formatting churn in old codebases while still letting projects standardize on tools such as Black, Ruff, isort, flynt, and pyupgrade.

### Timeline

- 2020: 0.1.0 and 1.0.0 were released.
- 2020: 1.2.2 added conda-forge availability.
- 2022: 1.4.0 added support for plain directories outside Git repositories.
- 2025: 3.0.0 added Ruff formatter support and changed default formatter dependencies.

### Related projects

- The README points to Black, Ruff, isort, flynt, pyupgrade, pytest-darker, Graylint, pre-commit, and the Darker GitHub Action as adjacent tools and integrations.

### Sources

- <https://github.com/akaihola/darker>
- <https://github.com/akaihola/darker/blob/master/CHANGES.rst>
- <https://github.com/akaihola/darker/releases>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: pyproject.toml

## Combined YAML source

View the package source record on GitHub. [combined/darker.yml](https://github.com/mxcl/pkgdb/blob/main/combined/darker.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph