PyPI · pypi.org

pex

Py Import Time Subprocess: subprocess call — process spawning.

Why PkgRadar flagged 2.96.0

Severity	Signal	Evidence
medium	Py Import Time Subprocess	subprocess call — process spawning. · pex-2.96.0/build-backend/pex_build/__init__.py
medium	Py Import Time Subprocess	subprocess call — process spawning. · pex-2.96.0/pex/vendor/__init__.py
medium	Py Import Time Subprocess	subprocess call — process spawning. · pex-2.96.0/testing/__init__.py
medium	Py Import Time Eval Exec	Python eval()/exec() called on a string. · pex-2.96.0/pex/vendor/_vendored/pip/pip/_vendor/pkg_resources/__init__.py
medium	Py Import Time Eval Exec	Python eval()/exec() called on a string. · pex-2.96.0/pex/vendor/_vendored/setuptools/pkg_resources/__init__.py
medium	Py Custom Build Backend	Non-standard PEP 517 build-backend `pex_build.setuptools.build` — runs custom code at install time. · pyproject.toml

Scanned versions

Version	Verdict	Score	Scanned (UTC)
`2.96.0`	Review	33	2026-06-01

Block this in CI

PkgRadar gates pex (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem pypi pex==2.96.0