manypkg

Manypkg is a package.json linter for JavaScript and TypeScript monorepos, with commands for checking, fixing and running work across packages. It suits teams that want package-level consistency checks without adopting a larger build system. Its focused scope is useful, but it does not provide task graphs, affected-build analysis or remote caching.

Overview

Manypkg supports Yarn, npm, pnpm, Bun and Lerna monorepos. Its central job is to catch package configuration problems: inconsistent dependency ranges, incorrect internal dependency versions, unsorted dependencies and other package-level issues. That makes it a practical fit for repositories where package metadata is the pain point, rather than build orchestration.

The command line separates checking from fixing. manypkg check reports repository errors and exits with a code, making it suitable for automated checks. manypkg fix also corrects issues it can handle automatically; problems outside that set still need attention. The project is MIT-licensed, and its README documents installation with Yarn or npm.

Key features

Package consistency checks

Manypkg checks that external dependency ranges match across packages, excluding peer dependencies, and that internal dependency ranges include the version of the referenced package. It also checks alphabetical dependency sorting. These rules help keep package manifests coherent, but do not amount to a general build or dependency-graph system.

Other checks cover peer and development dependency relationships, production dependencies in the root package, duplicate dependency types, package names and repository fields. This breadth makes the linter more useful than a single-purpose version check, while keeping its work centered on package.json files.

Commands and configuration

manypkg run runs a script for a package selected by partial name or directory. manypkg exec executes a CLI command across packages. These commands reduce the need to address each package individually, though they do not offer affected-build selection or remote caching.

Configuration lives in the root package.json. Teams can set a default branch, ignore selected rules and control whether the workspace: protocol is required or allowed; allowing it is the default. This gives maintainers room to adapt checks to repository conventions without making the tool's scope broader.

Pricing

Manypkg is free: its MIT-licensed CLI package costs nothing, with installation through Yarn or npm. There are no paid tiers, trial period or seat and usage caps to weigh against a cheaper plan. The trade-off is scope, not a feature tier: teams needing task graphs, affected builds or remote caching will need another tool alongside it or instead.

Platforms

Manypkg supports Linux, macOS and Windows. Its package-manager coverage includes Yarn, npm, pnpm and Bun; the README also names Lerna monorepos. The repository root declares Yarn 1.22.22 as its package manager.

Who it's for

Choose Manypkg if you maintain a supported monorepo and want automated checks for package names, dependency relationships, versions, sorting and repository metadata, plus commands to run scripts or CLI tools across packages. Its configuration is useful when a team needs to ignore specific rules or enforce a workspace protocol.

Look elsewhere if the main requirement is build orchestration, task graphs, affected-build detection or caching. Manypkg's package-level focus is a strength for teams that want a narrow linter, but it leaves those broader workflows to other software.

Pros and cons

Pros

• Checks a broad set of package.json conventions, including external and internal dependency ranges, package names and dependency relationships.
• Can automatically fix issues it recognizes, while its check command reports errors and exits with a code for use in automated workflows.
• Supports package-level script and CLI execution across monorepos using run and exec commands.
• Free and MIT-licensed, with configurable ignored rules and workspace-protocol behavior.

Cons

• Does not provide task graphs, affected builds or remote caching, limiting its usefulness as a complete monorepo build system.
• Automatic fixes apply only to problems that can be fixed automatically; other reported issues require manual work.
• Dedicated support terms and security or compliance claims are not part of its stated offering.

Alternatives

Browse Monorepo Management Tools for more options in this category. Pick npm instead when public package publishing and registry access are the priority; its free plan covers unlimited public packages, while paid plans are also offered.

Bazel is the better fit for teams seeking an open-source build and test tool rather than package.json linting. For a package manager with no paid plans or stated usage limits, consider Yarn. Nx is an alternative with a free Hobby plan that includes monthly credits, contributor and concurrent CI limits, and community support.

FerrFlow, affected, bento and Bit are also alternatives to compare for monorepo management.

Verdict

Manypkg is a good choice for teams that want a free, focused linter to keep monorepo package manifests consistent and run commands across packages. Its strongest reason to choose it is the combination of targeted checks, some automatic fixes and straightforward configuration. Choose another tool if you need build graphs, affected-build workflows or remote caching.