Read 2026-11-03
blacklanternsecurity/bbot: technical due diligence, read from its repository
What Borehole read in blacklanternsecurity/bbot's code and history at a6fb827: 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 |
What the repository says
LICENSE: Relicensed: GPL-3.0 → AGPL-3.0 (2025-12-09)AGENTS.md:84: states a policy on AI-generated contributions.gitmodules:1: 1 submodule(s) this survey does not read: bbot/modules/playground
Architecture & Codebase — including AI provenance
strongbbot/core/helpers/misc.py is 3,017 lines, 32× this codebase's median file
adequateThe median source file here is 94 lines. 8 files exceed 1,000 lines, the largest being 3,017. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
bbot/core/helpers/misc.py:1 — 3,017 lines (32× median) |
bbot/core/event/base.py:1 — 2,483 lines (26× median) |
bbot/modules/base.py:1 — 2,007 lines (21× median) |
bbot/modules/internal/excavate.py:1 — 1,718 lines (18× median) |
bbot/scanner/scanner.py:1 — 1,526 lines (16× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (.github/workflows/distro_tests.yml). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
.github/workflows/distro_tests.yml:54 — test retry |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key. 10 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| JWT, where fakes are usual |
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.
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate9 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 1 step pipes a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/benchmark.yml:33 — action pinned by tag |
.github/workflows/cla.yml:14 — action pinned by tag |
.github/workflows/distro_tests.yml:42 — download piped into a shell |
15 locked dependencies have published vulnerabilities, 17 high or critical in what ships
adequate15 of 139 locked dependencies match 66 published advisories in OSV, 31 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.
Relicensed: GPL-3.0 → AGPL-3.0 (2025-12-09)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
10 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-07-08. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version.
| 2026-07-08: GHSA-xpf3-p7gm-7756 (low), fixed in 3.0.0: BBOT's Symlink guard bypass in unarchive module allows planting symlinks during extraction |
| 2026-07-08: PYSEC-2026-3720 (low), fixed in 3.0.0: |
| 2026-06-17: GHSA-3mp7-vp6j-2mxx (low), fixed in 2.8.5: BBOT: Server-Side Request Forgery (SSRF) in docker_pull module via WWW-Authenticate realm parsing |
| 2026-06-17: GHSA-3vgw-585j-4m45 (moderate), fixed in 2.8.5: BBOT: Path traversal (Zip-Slip) in unarchive module - incomplete fix for CVE-2025-10284 |
| 2026-06-17: GHSA-m54h-vhf9-3w3m (moderate), fixed in 2.8.6: BBOT: Arbitrary File Write in postman_download Module |
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 blacklanternsecurity/bbot: 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.