Read 2026-11-03
scipag/vulscan: technical due diligence, read from its repository
What Borehole read in scipag/vulscan's code and history at bd642ed: 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 | adequate |
| Engineering Process & SDLC Maturity | not assessable |
| Product & Engineering Maturity | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateCommit messages are templated rather than written
adequate61% of commit subjects are exact repeats of another subject, and subject length varies by only 10.3 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.
| 34× 'DB Update' |
| 8× 'Update README.md' |
| 4× 'Update update.sh' |
1 base image floats: no version, or `latest`
adequate1 of 1 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
utilities/docker/Dockerfile:1 — base image without a version |
Engineering Process & SDLC Maturity
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.
Product & Engineering Maturity
not assessableNot rated: only 2 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
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.
utilities/docker/Dockerfile — runs as root |
Observability & Operations
not assessableNot rated: only 3 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 scipag/vulscan: 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.