Read 2026-11-03
pycqa/bandit: technical due diligence, read from its repository
What Borehole read in pycqa/bandit's code and history at 48ef27b: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate6 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
doc/requirements.txt:4 — >=4.0.0 |
doc/requirements.txt:5 — >=0.3.0 |
doc/requirements.txt:6 — any version |
requirements.txt:4 — >=5.3.1 |
requirements.txt:5 — >=1.20.0 |
1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
docker/Dockerfile — runs as root |
4 shell commands built from strings
adequate4 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
bandit/plugins/injection_shell.py:175 — command run through a shell |
bandit/plugins/injection_shell.py:184 — command run through a shell |
bandit/plugins/injection_shell.py:191 — command run through a shell |
6 deserialisers that can run code
adequate6 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
bandit/formatters/html.py:126 — code-executing deserialiser |
bandit/formatters/json.py:46 — code-executing deserialiser |
bandit/formatters/screen.py:23 — code-executing deserialiser |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on pycqa/bandit: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.