build
A simple, correct Python build frontend
Decision gist · record as of 2026-08-14
Yes. build is a foundational tool for modern Python packaging—actively maintained, low-friction to install, and widely used in CI/CD and package tooling. The MIT license imposes no restrictions. Install it if you build or distribute Python packages, integrate with packaging tools, or need reliable PEP 517 compliance. Not necessary for end-users installing pre-built wheels.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; pyproject.toml must be present in the project root.
- Low friction install with five runtime dependencies (packaging, pyproject_hooks, colorama, importlib-metadata, tomli).
- Active maintenance with recent releases; last commit 2026-08-13.
License · maintenance · safety
MIT (permissive) — MIT license (permissive) allows unrestricted use, modification, and distribution in both open and closed projects with minimal attribution requirements.
last release 2026-04-30 (106 days) · last repo commit 2026-08-13 · 854 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 158,054,202 downloads/mo, #258 on PyPI
Alternatives
Verify before relying
pip install build
python -m build
# or
python -m build --wheel --sdist --outdir dist/- Whether build isolation works correctly with all PEP 517 backend implementations in practice.
- Performance characteristics when building large projects or with complex dependency trees.
- Compatibility with non-standard pyproject.toml configurations or legacy setup.py fallbacks.
- Support for editable installs and how they interact with the isolation mechanism.
What it is and what it does
build is a PEP 517-compliant build frontend that automates the creation of Python wheels and source distributions from modern pyproject.toml-based projects. It handles the complexity of setting up isolated build environments, managing build dependencies, and invoking the appropriate backend without requiring manual configuration. The tool runs as a command-line utility (python -m build or pyproject-build) and outputs compiled artifacts to a dist/ directory by default.
The package is designed for package maintainers, CI/CD systems, and tools that need to build Python distributions reliably. It supports PEP 517 config settings, alternative installers (pip or uv), metadata extraction, and optional build isolation bypass for development workflows. Its five runtime dependencies (packaging, pyproject_hooks, colorama, importlib-metadata, tomli) keep the installation lightweight while providing the hooks and metadata parsing needed for standards-compliant builds.
Use it for
- Building wheels and sdists in CI/CD pipelines without manual environment setup or dependency resolution.
- Integrating with tools like pipx or uv to create reproducible builds across platforms.
- Extracting package metadata as JSON for version detection or dependency analysis in automation scripts.
- Developing Python packages locally with isolated builds to verify that pyproject.toml correctly declares all build dependencies.
- Disabling isolation in development workflows to test against local editable installs or custom backends.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
build is a foundational tool for modern Python packaging—actively maintained, low-friction to install, and widely used in CI/CD and package tooling. The MIT license imposes no restrictions. Install it if you build or distribute Python packages, integrate with packaging tools, or need reliable PEP 517 compliance. Not necessary for end-users installing pre-built wheels.
Install
build on PyPI
Before you install
Low friction install with five runtime dependencies (packaging, pyproject_hooks, colorama, importlib-metadata, tomli). Active maintenance with recent releases; last commit 2026-08-13. Requires Python 3.10 or later.
Requires Python 3.10 or later; pyproject.toml must be present in the project root.
License in practice
MIT license (permissive) allows unrestricted use, modification, and distribution in both open and closed projects with minimal attribution requirements.
Quickstart
pip install build
python -m build
# or
python -m build --wheel --sdist --outdir dist/Verify before relying
- Whether build isolation works correctly with all PEP 517 backend implementations in practice.
- Performance characteristics when building large projects or with complex dependency trees.
- Compatibility with non-standard pyproject.toml configurations or legacy setup.py fallbacks.
- Support for editable installs and how they interact with the isolation mechanism.
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 5 packagespackagingpyproject_hookscoloramaimportlib-metadatatomli |
| Maintenance | Actively maintained 106 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 158,054,202 / month, #258 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Programming Language :: Python :: 3Programming Language :: Python :: 3 :: OnlyProgramming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14Programming Language :: Python :: Implementation :: CPythonProgramming Language :: Python :: Implementation :: PyPy |
Evidence: build-1.5.0-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “isolated wheel builder”
- buildBuilds Python packages in isolated environments, generating wheels…
- poetry-corepoetry-core is a PEP 517 build backend that enables build frontends…
- nodeenvnodeenv creates isolated Node.js environments similar to Python's…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also twine · wheel-stub · pep517 · pbs-installer · pdm-pep517 · whey · cmeel · pipx · virtualenv · installer