PkgRadar

PyPI · pypi.org

hyperforge

Py Custom Build Backend: Non-standard PEP 517 build-backend `uv_build` — runs custom code at install time.

Why PkgRadar flagged 1.0.0.post48

SeveritySignalEvidence
mediumPy Custom Build BackendNon-standard PEP 517 build-backend `uv_build` — runs custom code at install time. · pyproject.toml

Scanned versions

VersionVerdictScoreScanned (UTC)
1.0.0.post48Review152026-06-08
1.0.0.post46Review152026-06-07
1.0.0.post44Review152026-06-07
1.0.0.post39Low risk02026-06-04
1.0.0.post34Low risk02026-06-02
1.0.0.post33Low risk02026-06-02
1.0.0.post32Low risk02026-06-02
1.0.0.post31Low risk02026-06-02
1.0.0.post27Low risk02026-06-02
1.0.0.post26Low risk02026-06-02
1.0.0.post25Low risk02026-06-02
1.0.0.post20Low risk02026-06-02
1.0.0.post19Low risk02026-06-02

Block this in CI

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

pkgradar gate --ecosystem pypi hyperforge==1.0.0.post48
Start free — 25 scans / moView full evidence