Read 2026-11-03
ever-co/ever-traduora: technical due diligence, read from its repository
What Borehole read in ever-co/ever-traduora's code and history at ff81a5d: 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
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongdocs-website/static/js/swagger-ui.js is 20,396 lines, 463× this codebase's median file
adequateThe median source file here is 44 lines. 3 files exceed 1,000 lines, the largest being 20,396. 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.
docs-website/static/js/swagger-ui.js:1 — 20,396 lines (463× median) |
docs-website/static/js/swagger-ui-standalone-preset.js:1 — 14,809 lines (336× median) |
api/src/migrations/1537531930470-add locales.ts:1 — 1,753 lines (39× median) |
35 errors caught and discarded in product code
adequate35 places catch an error and do nothing with it, across 2 files (0.5 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.
docs-website/static/js/swagger-ui-standalone-preset.js:7 — error caught and discarded |
docs-website/static/js/swagger-ui-standalone-preset.js:17 — error caught and discarded |
docs-website/static/js/swagger-ui-standalone-preset.js:2000 — error caught and discarded |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v0.22.0, is not on the branch this survey read; the newest release on it is v0.21.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.22.0 |
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 |
The build runs third-party code it does not pin
adequate3 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. 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/k8s-build.yml:27 — action pinned by tag |
.github/workflows/k8s-build.yml:28 — action pinned by tag |
132 locked dependencies have published vulnerabilities, 10 high or critical in what ships
adequate132 of 4,262 locked dependencies match 237 published advisories in OSV, 110 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
api/yarn.lock — handlebars 4.7.7: GHSA-2w6w-674q-4c4q (critical), fixed in 4.7.9 |
webapp/yarn.lock — piscina 3.1.0: GHSA-67c8-pqhq-4rmx (critical), fixed in 5.3.2 |
yarn.lock — piscina 4.8.0: GHSA-67c8-pqhq-4rmx (critical), fixed in 4.9.4 |
6 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-10-25. 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-10-25: GHSA-gp83-wv43-h962 (moderate), fixed in 0.23.0: Account with an unverified email is added to projects it is invited to |
| 2026-10-25: GHSA-vjr4-28gx-35p8 (critical), fixed in 0.23.0: Default admin account created with a published password |
| 2026-10-25: GHSA-cx96-m99q-j695 (moderate), fixed in 0.22.0: Project administrator can change or delete invitations belonging to another project |
| 2026-10-25: GHSA-pfvf-33wh-gwwr (high), fixed in 0.22.0: Unverified signup can claim pending project invitations |
| 2026-10-25: GHSA-w5wm-pf8g-hmgc (high), fixed in 0.22.0: Default JWT Signing Secret ('secret') Enables Token Forgery and Project Privilege Escalation |
Observability & Operations
adequateNo 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 420 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 |
An error reporter is installed but never initialised
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.
deploy/k8s/traduora-preview.yaml:45 — image without a version |
Readiness and liveness probes are identical in 1 of 1 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
deploy/k8s/traduora-preview.yaml — same probe endpoint twice |
1 of 1 deployments run a single replica
adequate1 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
deploy/k8s/traduora-preview.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on ever-co/ever-traduora: 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.