Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

affected

github.com

  • Free plan
  • Windows
  • macOS
  • Linux
7.4 Club score Visit github.com

What affected is

affected is a free, MIT-licensed command-line tool that finds monorepo packages affected by Git changes and can run tests or other commands for them. It traces transitive dependencies and can explain the chain from a change to an affected package. The README describes automatic project-type and dependency-graph detection for getting started without configuration. Listed ecosystems include Cargo, npm, pnpm, Yarn, Bun, Go, Python, Maven, Gradle, .NET, Swift, Dart/Flutter, Elixir, and Scala/sbt. Commands cover listing packages, testing, running commands, graphing, CI, initialization, and watch mode. Work can run in parallel, with dry-run previews, timeouts, package filters, and skip patterns. Output options include JSON, JUnit XML, shell completions, a Unicode dependency tree, and DOT graphs. CI output supports GitHub Actions, GitLab, CircleCI, Azure Pipelines, and generic key-value output; GitHub Actions also has setup, dynamic matrices, and a companion action for pull-request comments. Installation options include package managers, GitHub Actions, and release binaries. It runs on Linux, macOS, and Windows; contributions and issue reports are directed to the repository.

Who it suits

affected is suited to developers maintaining monorepos who want to target tests or commands at packages touched by Git changes. Its CI formats and GitHub Actions support also suit teams integrating that workflow into builds.

Good to know, and what to watch

  • Traces transitive dependencies and explains affected-package chains.
  • Supports a broad list of language ecosystems.
  • Parallel execution, dry runs, timeouts, and filters.
  • CI output supports several named providers.
  • Runs on Linux, macOS, and Windows.
  • It is a standalone CLI.
  • Issue reporting and contributions go through its repository.

affected

Free

Open source

Getting started

  1. Install affected through Homebrew, uv, pipx, pip, Cargo, GitHub Actions or a release binary
  2. Let it auto-detect the project type and dependency graph
  3. Use the list command to inspect packages
  4. Run test or run against affected packages
  5. Configure CI output or GitHub Actions integration as needed

Limits to check

The free affected plan is the MIT-licensed standalone CLI. Its listed operating systems are Linux, macOS and Windows.

The Club's review

affected is an open-source command-line tool for targeting monorepo work at packages touched by Git changes. It suits developers and teams whose repositories span multiple package ecosystems and who want to avoid running every check on every change. Its strength is focused, dependency-aware targeting with useful CI output; it is not a substitute for a broader monorepo management platform.

Overview

affected traces direct and transitive dependencies to identify packages that may need tests or other commands, and can show the dependency chain behind its selection. That explanation helps teams review why a downstream package is included rather than treating the result as an unexplained list. Automatic project-type and dependency-graph detection lowers the effort to get started, though teams still decide which commands to run and how to incorporate them into their workflow.

The CLI includes list, test, run, graph, ci, init and watch commands. Parallel execution, dry-run previews, timeouts, package filters and skip patterns give maintainers control over targeted runs. This is a useful toolkit for teams already comfortable with CLI and CI workflows, but it does not remove the need to design those workflows.

Key features

Multi-ecosystem package detection

Support spans Cargo, npm, pnpm, Yarn, Bun, Go, Python, Maven, Gradle, .NET, Swift, Dart/Flutter, Elixir and Scala/sbt. The package-manager coverage also names Poetry and uv for Python, Mix for Elixir, and SPM for Swift. This breadth is a practical advantage for mixed-language repositories; teams should still confirm that their particular package layout fits the ecosystems supported.

CI and review workflows

CI output supports GitHub Actions, GitLab, CircleCI, Azure Pipelines and generic key-value output. The documented GitHub Actions setup can build dynamic job matrices for affected packages, while a companion action can post and update pull-request comments with package names and reasons. These integrations can make change-aware checks visible to both automation and reviewers, especially in GitHub-based workflows.

Execution and output controls

Commands can run across multiple jobs in parallel, with dry-run previews, timeouts, package filters and skip patterns for controlling execution. JSON and JUnit XML output suit automation, while shell completions, a Unicode dependency tree and DOT graph output help with CLI use and dependency inspection. These are useful options for teams integrating the tool into existing pipelines, rather than a turnkey interface for users who prefer graphical workflow management.

Pricing

affected costs nothing. The free plan is the standalone CLI, and the software is MIT-licensed open source. There is no paid tier in the plan described, so teams can use its task graph and affected builds without a subscription; they also take on the responsibility of installing and integrating a command-line tool themselves.

Installation options include Homebrew, uv, pipx, pip, Cargo, GitHub Actions and binaries from Releases. The project welcomes contributions and directs users to GitHub issues for support, making it a fit for teams comfortable with an open-source project and community-oriented support rather than a paid support plan.

Platforms

affected runs on Linux, macOS and Windows. Its CLI distribution options make it viable across common developer environments, while CI integrations address several hosted pipeline formats and generic key-value output.

Who it's for

Choose affected if you maintain a monorepo and want dependency-aware targeting across one or more of its supported ecosystems, particularly when CI time or unnecessary package-level runs are a concern. Its explanation of dependency chains and range of output formats also suit teams that need to understand and automate package selection.

Look elsewhere if you want a wider monorepo management environment rather than a CLI focused on affected-package detection and command execution. Teams that do not want to configure command-line and CI workflows may also prefer a more integrated platform.

Pros and cons

  • Broad ecosystem support: named ecosystems range from JavaScript package managers to Go, Python, .NET and Scala, making the tool relevant to varied monorepos.
  • Transparent dependency targeting: transitive analysis and chain explanations help teams inspect why a package was selected.
  • Useful automation controls: parallel jobs, dry runs, timeouts, filters and skip patterns let maintainers shape command execution.
  • CLI-first scope: teams must choose commands and build their own workflow around the tool; it is not a general monorepo management interface.
  • Open-source support model: contributions and GitHub issues provide project channels, but the plan does not include a paid support tier.

Alternatives

Monorepo Management Tools is a useful place to compare options if affected's focused CLI scope does not cover the broader management needs of your repository.

Pick Nx instead if you want a freemium option with a free Hobby plan capped at 5 contributors and 10 concurrent CI connections, alongside 50,000 credits reset monthly. Lerna is another free option with a Hobby plan offering 50,000 monthly credits, 5 contributors and 10 concurrent CI connections; it may suit teams comparing an alternative monorepo workflow with those limits.

npm is the closer choice when the need is publishing or using public packages: its free plan includes unlimited public packages and public registry access for public package authors, rather than affected's package targeting. bento is worth considering if stored capacity and retention are the priority: its free plan includes 10 GB stored with 14-day retention.

Bit offers an open-source option and free personal use through Bit Cloud. Blaze is another free option described as free to use. Bun may suit teams looking for an open-source JavaScript runtime and toolkit instead. EvoMaster is an open-source tool with no monetary cost or paid external services required.

Verdict

Choose affected for a free, MIT-licensed way to identify changed monorepo packages, follow their dependency impact and direct commands through common CI workflows. Its broad ecosystem support and execution controls make it a strong fit for teams willing to work in the CLI. Look elsewhere if you need a broader monorepo management platform or prefer not to build your own command and CI workflow around a focused tool.

The verdict

affected focuses on identifying changed monorepo packages and directing commands toward them. Its ecosystem coverage and CI options are useful considerations for teams choosing a package-aware workflow.

Questions people ask

What does affected do?

It finds monorepo packages affected by Git changes and runs tests or other commands on them.

Which ecosystems does it support?

Supported ecosystems include Cargo, npm, pnpm, Yarn, Bun, Go, Python, Poetry, uv, Maven, Gradle, .NET/C#, Swift/SPM, Dart/Flutter, Elixir/Mix and Scala/sbt.

Does affected integrate with CI systems?

Yes. Its CI output supports GitHub Actions, GitLab, CircleCI, Azure Pipelines and generic key-value output.

How can affected be installed?

The README documents Homebrew, uv, pipx, pip, Cargo, GitHub Actions and release-binary installation.

Which operating systems can run it?

It runs on Linux, macOS and Windows.

Is affected open source?

Yes. The repository identifies it as MIT licensed and lists the free plan at no cost.

What the maker publishes

CI integrations
Its CI output supports GitHub Actions, GitLab, CircleCI, Azure Pipelines and generic key-value output. source
Commands
The CLI provides list, test, run, graph, ci, init and watch commands. source
Dependency analysis
It traces transitive dependencies to identify packages affected by a change and can explain the dependency chain. source
Distribution
The README documents installation through Homebrew, uv, pipx, pip, Cargo, GitHub Actions or a binary downloaded from Releases. source
Ecosystems
It lists support for Cargo, npm, pnpm, Yarn, Bun, Go, Python, Maven, Gradle, .NET, Swift, Dart/Flutter, Elixir and Scala/sbt. source
Execution
Commands can run in parallel across multiple jobs, and the CLI supports dry-run previews, timeouts, package filters and skip patterns. source
GitHub Actions
The README documents a setup action and dynamic CI job matrices for affected packages. source
License
The repository identifies the software as MIT licensed. source
Outputs
The CLI supports JSON output, JUnit XML, shell completions and a Unicode dependency tree, with DOT graph output also available. source
PR comments
A companion GitHub Action can post and update pull request comments showing affected packages and reasons. source
Purpose
affected detects which monorepo packages are affected by Git changes and runs tests or other commands on those packages. source
Setup
The README says it auto-detects project type and dependency graph with zero configuration to start. source
Support
The README welcomes contributions and directs users to the repository's GitHub issues. source

Checked against the maker's pages on 3 Oct 2026.