PkgRadar

PyPI · pypi.org

brickforge

Py Install Time Subprocess: subprocess call — process spawning.

Why PkgRadar flagged 0.1.0a35

SeveritySignalEvidence
mediumPy Install Time Subprocesssubprocess call — process spawning. · brickforge-0.1.0a35/brickforge/routes/setup.py
mediumPy Install Time Subprocesssubprocess call — process spawning. · brickforge-0.1.0a35/setup.py
highPy Install Time Network CallNetwork call (urllib/requests/httpx/http.client) at install or import time. · brickforge-0.1.0a35/brickforge/routes/setup.py

Scanned versions

VersionVerdictScoreScanned (UTC)
0.1.0a35High risk862026-06-09
0.1.0a34High risk862026-06-05
0.1.0a33High risk862026-06-04
0.1.0a32High risk862026-06-01
0.1.0a31High risk862026-05-30
0.1.0a30High risk862026-05-30
0.1.0a29High risk862026-05-30
0.1.0a27High risk862026-05-30
0.1.0a26High risk862026-05-30
0.1.0a25High risk862026-05-30
0.1.0a24High risk862026-05-30
0.1.0a23High risk862026-05-30
0.1.0a22High risk862026-05-30
0.1.0a21High risk862026-05-30
0.1.0a20High risk862026-05-30
0.1.0a19High risk862026-05-30
0.1.0a18High risk862026-05-30
0.1.0a16High risk862026-05-30
0.1.0a15High risk862026-05-30
0.1.0a14High risk862026-05-30
0.1.0a13High risk862026-05-30
0.1.0a12High risk862026-05-30
0.1.0a11High risk862026-05-30
0.1.0a10High risk862026-05-30
0.1.0a9High risk862026-05-30
0.1.0a8High risk862026-05-30

Block this in CI

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

pkgradar gate --ecosystem pypi brickforge==0.1.0a35