Bandit
8,399Security linter for Python. Catches common code-level vulnerabilities.
Activity band details
Activity band A to F: a bin of a score that adds GitHub stars (log scale), a push to the upstream repository in the 12 months before `as_of`, the number of declared integration surfaces and, where the catalogue records them, citing papers and benchmark evaluations. It measures popularity and activity. It is not a level of evidence: no band means a paper cites the tool or that it was measured. Recency is judged as of 2026-11-22.
Computed band: B
(raw score 6.57).
Shown band: B
.
Facets:
documented_in=0evaluated_on=2integration_surfaces=1paper_citations=0recent_push=2stars=1.57
Source of truth: pipeline/maturity/score.py
Measured on SAICA-Bench in this configuration
Each row is one run of Bandit, set up by us as its run card says, on one labelled set of faulty and clean samples (how we test). It says what that configuration flagged on that set, not how good Bandit is in general: another model, another input or the tool's own defaults could score differently. J = TPR - FPR, on the answers that carry a verdict. 0% is chance, 100% flags every bad sample and no clean one. J is the sort key within a mode; each row also has false alarms per 100 clean changes and precision at 1%, 5% and 20% prevalence.
| Set | Configuration and run card | J (95% interval) | TPR | FPR | No verdict | Cost per 1,000 reviews |
|---|---|---|---|---|---|---|
|
Security vulnerability
Real agent output
|
bandit (assert check B101 skipped, test files left out)
Catalog tool · Free program · own check · outside design scope
Not ranked: outside the tool's design scope: a pattern scanner: most flaws in this set are missing checks and logic-level flaws that its patterns do not describe.
How this run differs from the tool's defaults
|
+1.3%
−5.3% to +7.7%
|
14.5% | 13.2% | 51 | $0 |
|
Security vulnerability
Real agent output
|
bandit (default profile)
Catalog tool · Free program · own check · outside design scope
Not ranked: outside the tool's design scope: a pattern scanner: most flaws in this set are missing checks and logic-level flaws that its patterns do not describe.
How this run differs from the tool's defaults
|
−7.7%
−16.0% to +0.6%
|
19.2% | 26.8% | 51 | $0 |
An answer with no verdict (failed call, blocked request, text cut by the token budget, no verdict in the text) is unreadable: it is left out of the rates and counted beside them, per label. “~” marks an estimated cost. SAICA-Bench results v2.0.0, built 2026-11-22.
Description
Bandit is a Python security linter from PyCQA: it walks the AST looking for common insecure patterns — hardcoded passwords, use of eval/exec, weak crypto primitives, shell-injection-prone subprocess calls, insecure deserialization, and so on. It runs from the CLI and in CI as a post_generation security gate. Configuration lives in pyproject.toml [tool.bandit], which the audit detector now recognises.
Why it's included
Occupies detection × post_generation × fully_autonomous for security_vulnerability in the Python lane. Distinct from Semgrep because Bandit is Python-specific with hand-tuned rules covering Python's standard library footguns; including it lets the audit detector resolve [tool.bandit] blocks.
Security notes
Standard dev-tool security posture; Bandit runs locally against source and does not execute target code. Like all rule-based scanners it produces both false positives and false negatives — pair it with a complementary scanner (e.g. semgrep) on regulated codepaths.
Addresses failure modes
These tags are the catalog's claim about what Bandit is built to catch or prevent. A tag is not a test result. The rows under Measured on SAICA-Bench are the evidence, for the sets and the configuration we ran.
- Security vulnerability — Insecure patterns, injection flaws, weak cryptography, secret leakage.