pbr
Python Build Reasonableness
Install
pbr on PyPI
pip
pip install pbruv
uv add pbrpoetry
poetry add pbrPackage facts
| License | Apache-2.0 (permissive) |
| Python support | supports the current Python release (>=2.6) |
| Install friction | low — pure-Python wheel |
| Runtime dependencies | 1 — setuptools |
| Maintenance | aging — 283 days since the last release |
| First released | |
| Popularity | one of the top 1,000 most-downloaded packages on PyPI (30-day window, as of 2026-08-13) |
| Known vulnerabilities | none known (OSV.dev, checked 2026-08-13) |
Evidence: pbr-7.0.3-py2.py3-none-any.whl
About pbr
from the package's own PyPI description — quoted content, verbatim
Introduction
.. image:: https://img.shields.io/pypi/v/pbr.svg :target: https://pypi.python.org/pypi/pbr/ :alt: Latest Version
.. image:: https://img.shields.io/pypi/dm/pbr.svg :target: https://pypi.python.org/pypi/pbr/ :alt: Downloads
PBR is a library that injects some useful and sensible default behaviors
into your setuptools run. It started off life as the chunks of code that
were copied between all of the OpenStack_ projects. Around the time that
OpenStack hit 18 different projects each with at least 3 active branches,
it seemed like a good time to make that code into a proper reusable library.
PBR is only mildly configurable. The basic idea is that there's a decent way to run things and if you do, you should reap the rewards, because then it's simple and repeatable. If you want to do things differently, cool! But you've already got the power of Python at your fingertips, so you don't really need PBR.
PBR also aims to maintain a stable base for packaging. While we occasionally deprecate features, we do our best to avoid removing them unless absolutely necessary. This is important since while projects often do a good job of constraining...
Read as markdown · JSON record · Source repository · Homepage · Docs
AI interpretation — verify before relying
AI-generated interpretation of the package facts above; every digit, version, license, or vulnerability id it cites is grounded in the facts already shown on this page
PBR injects sensible defaults into setuptools to simplify Python package configuration and release management, automating common build and versioning tasks across projects.
Low friction install with a single runtime dependency on setuptools. Maintenance status is aging (283 days since last release), but the package is marked Production/Stable and has maintained backward compatibility as a deliberate design principle.
Licensed under Apache License 2.0 (permissive), allowing commercial and private use with minimal restrictions; suitable for most projects that can accommodate attribution.
Usage
pip install pbr
# In setup.py:
from pbr.setup import setup
setup()
Requires setuptools as a runtime dependency; intended for use during package build/install, not runtime application code.
Verdict: PBR is a stable, widely-adopted setuptools plugin (top 1000 PyPI) with no known vulnerabilities and permissive licensing. Its aging maintenance status and 283-day release cycle are typical for a mature, feature-complete tool. Best suited for projects already aligned with OpenStack conventions; low installation friction makes adoption straightforward.
Needs verification
- Whether the aging maintenance status reflects intentional stability or reduced active development.
- Compatibility details with modern Python packaging standards (PEP 517/518) beyond the description's mention of attempted support.
Similar packages
permissive · top 1,000 on PyPI
packageurl-pythonpermissive · top 1,000 on PyPI
pytest-runnerpermissive · top 1,000 on PyPI
poetry-corepermissive · top 1,000 on PyPI
lockfilepermissive · top 1,000 on PyPI
rfc3986permissive · top 1,000 on PyPI
setuptools-scmpermissive · top 1,000 on PyPI
glompermissive · top 1,000 on PyPI
buildpermissive · top 1,000 on PyPI
pexpectpermissive · top 1,000 on PyPI