Borehole · Project · free tier
sqlmapproject/sqlmap
Free reading: not for reliance
c9745f8 · 11,119 commits · 895 files
Read 2026-10-23

sqlmapproject/sqlmap: technical due diligence, read from its repository

What Borehole read in sqlmapproject/sqlmap's code and history at c9745f8: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturityadequate
Security & Reliability Postureadequate
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong
01.3

Commit messages are templated rather than written

adequate

31% of commit subjects are exact repeats of another subject, and subject length varies by only 39.7 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.

Evidence
426× 'Minor update'
373× 'minor update'
244× 'Minor patch'
01.6

lib/core/common.py is 6,011 lines, 89× this codebase's median file

adequate

The median source file here is 67 lines. 18 files exceed 1,000 lines, the largest being 6,011. 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.

Evidence
lib/core/common.py:1 — 6,011 lines (89× median)
lib/core/option.py:1 — 3,256 lines (48× median)
lib/utils/gui.py:1 — 1,912 lines (28× median)
lib/controller/checks.py:1 — 1,893 lines (28× median)
lib/request/connect.py:1 — 1,870 lines (27× median)
01.15

364 errors caught and discarded in product code

adequate

364 places catch an error and do nothing with it, across 113 files (1.7 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.

Evidence
extra/beep/beep.py:36 — error caught and discarded
extra/boundarycheck/boundarycheck.py:151 — error caught and discarded
extra/boundarycheck/boundarycheck.py:240 — error caught and discarded

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

adequate
04.19

20% of bug fixes add or change a test

adequate

Of 169 fixes in the last 24 months, 33 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.

Evidence
33 of 169

Security & Reliability Posture

adequate
05.2

None of the standard security guard rails are configured

adequate

There is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.

Evidence
checked 5 kinds of guard rail across 895 tracked files; 0 present
05.21

12 shell commands built from strings

adequate

12 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.

Evidence
extra/beep/beep.py:41 — command run through a shell
extra/beep/beep.py:44 — command run through a shell
extra/beep/beep.py:53 — command run through a shell

Observability & Operations

not assessable

Not 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on sqlmapproject/sqlmap: 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.