Read 2026-10-23
owasp/nettacker: technical due diligence, read from its repository
What Borehole read in owasp/nettacker's code and history at 14ef2b4: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: GPL-3.0 → Apache-2.0 (2017-08-27)AGENTS.md:50: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongnettacker/web/static/js/main.js is 1,194 lines, 27× this codebase's median file
adequateThe median source file here is 43 lines. 2 files exceed 1,000 lines, the largest being 1,194. 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.
nettacker/web/static/js/main.js:1 — 1,194 lines (27× median) |
nettacker/database/db.py:1 — 1,175 lines (27× median) |
31 errors caught and discarded in product code
adequate31 places catch an error and do nothing with it, across 6 files (0.6 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.
nettacker/core/arg_parser.py:763 — error caught and discarded |
nettacker/core/arg_parser.py:768 — error caught and discarded |
nettacker/core/arg_parser.py:773 — error caught and discarded |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate1 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 |
1 deserialiser that can run code
adequate1 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.
nettacker/core/messages.py:23 — code-executing deserialiser |
7 locked dependencies have published vulnerabilities, 11 high or critical in what ships
adequate7 of 84 locked dependencies match 49 published advisories in OSV, 11 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.
poetry.lock — aiohttp 3.13.3: GHSA-2g87-pp6c-29x5 (high), fixed in 3.14.4 |
poetry.lock — cryptography 41.0.7: GHSA-3ww4-gg4f-jr7f (high), fixed in 42.0.0 |
poetry.lock — pyopenssl 23.3.0: GHSA-5pwr-322w-8jr4 (high), fixed in 26.0.0 |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 326 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 326 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 326 files for 10 structured logging libraries; 0 matched |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on owasp/nettacker: 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.