Read 2026-11-03
gladysassistant/gladys: technical due diligence, read from its repository
What Borehole read in gladysassistant/gladys's code and history at ca702c3: 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 | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
.github/CONTRIBUTING.md:73: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongserver/utils/constants.js is 2,832 lines, 42× this codebase's median file
adequateThe median source file here is 67 lines. 10 files exceed 1,000 lines, the largest being 2,832. 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.
server/utils/constants.js:1 — 2,832 lines (42× median) |
server/services/mcp/lib/buildSchemas.js:1 — 2,063 lines (30× median) |
front/src/components/boxs/thermostat/ThermostatBox.jsx:1 — 2,033 lines (30× median) |
front/src/routes/scene/edit-scene/index.js:1 — 1,681 lines (25× median) |
server/services/thermostat/lib/thermostat.applySchedules.js:1 — 1,662 lines (24× median) |
Engineering Process & SDLC Maturity
adequate6% of recent commits change more than 2,000 lines
adequate46 of 818 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 46 commits over 2,000 lines |
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.
docker/Dockerfile — runs as root |
53 of 81 migrations cannot be rolled back
adequate53 schema migrations (65%) have no working way back: an empty `downgrade`, a `down` that does nothing, or a data migration with no reverse. A bad deploy that includes one is recovered from a backup, not reverted. Ask when a restore was last rehearsed.
server/migrations/20200123094438-add-triggers-attribute.js:11 — migration with no way back |
server/migrations/20200201125436-add-caldav-data.js:13 — migration with no way back |
server/migrations/20200207214849-add-calendar-event-url.js:10 — migration with no way back |
3 shell commands built from strings
adequate3 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.
server/cli/install_service_dependencies.js:29 — command run through a shell |
server/services/matter/lib/matter.backupController.js:29 — command run through a shell |
server/services/matter/lib/matter.restoreBackup.js:26 — command run through a shell |
36 locked dependencies have published vulnerabilities, 61 high or critical in what ships
adequate36 of 1,212 locked dependencies match 129 published advisories in OSV, 61 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.
server/services/nuki/package-lock.json — form-data 2.3.3: GHSA-fjxv-7rqg-78g4 (critical), fixed in 2.5.4 |
server/services/google-cast/package-lock.json — protobufjs 6.11.4: GHSA-xq3m-2v4x-88gg (critical), fixed in 8.0.1 |
server/package-lock.json — tar 6.2.1: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
2 workload settings give a container the host
adequate2 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
docker/docker-compose.yml:6 — privileged or host namespace |
docker/docker-compose.yml:7 — privileged or host namespace |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
front/vite.config.mjs:133 — source maps in a production build |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-21. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 5.3.1. Answer lives in: the release you run, set against each fixed version.
| 2026-09-21: CVE-2026-93340 (high): Gladys Assistant before 5.1.0 contains a password reset link poisoning vulnerability that allows unauthenticated remote attackers to obtain valid password reset |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 4,023 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 4,023 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 4,023 files for 10 structured logging libraries; 0 matched |
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 |
1 of 2 deployed images carry no version, or `latest`
adequate1 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker/docker-compose.yml:27 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on gladysassistant/gladys: 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.