Read 2026-11-03
enatega/food-delivery-multivendor: technical due diligence, read from its repository
What Borehole read in enatega/food-delivery-multivendor's code and history at d9eb29e: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| 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
strongenatega-multivendor-app/src/utils/country_codes.js is 2,555 lines, 63× this codebase's median file
adequateThe median source file here is 40 lines. 14 files exceed 1,000 lines, the largest being 2,555. 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.
enatega-multivendor-app/src/utils/country_codes.js:1 — 2,555 lines (63× median) |
enatega-multivendor-rider/lib/ui/useable-components/svg/welldone.tsx:1 — 2,334 lines (58× median) |
enatega-multivendor-web/lib/ui/screens/protected/order/checkout/index.tsx:1 — 1,718 lines (42× median) |
enatega-multivendor-app/src/apollo/queries.js:1 — 1,363 lines (34× median) |
enatega-multivendor-app/src/components/SubCategoryPage/SubCategoryPage.js:1 — 1,292 lines (32× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate31 test files against 3,091 source files (1.0%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 31 test files / 3,091 source files |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (enatega-multivendor-admin/cypress.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
enatega-multivendor-admin/cypress.config.ts:8 — test retry |
Product & Engineering Maturity
adequate86 direct dependencies in a single manifest
adequateenatega-multivendor-app/package.json declares 86 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
enatega-multivendor-app/package.json — 86 declared |
enatega-multivendor-store/package.json — 71 declared |
enatega-multivendor-rider/package.json — 70 declared |
enatega-multivendor-web/package.json — 37 declared |
Node.js 20 is past end of life
adequateThe code is pinned to Node.js 20 (end of life 2026-04-30). None of these receives security fixes any more; the first stopped on 2026-04-30. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
enatega-multivendor-admin/.nvmrc — Node.js 20, end of life 2026-04-30 |
1% of bug fixes add or change a test
adequateOf 468 fixes in the last 24 months, 4 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.
| 4 of 468 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v2.0.11, is not on the branch this survey read; the newest release on it is v2.0.9. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.0.11 |
Security & Reliability Posture
adequate9 credential-shaped strings committed to the tree
adequateMatches for Google API key appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when. Only Google API keys matched. Those are often public by design, in a browser app's Firebase or Maps configuration; the question is whether each is restricted to the app's domains and APIs.
| 5 cited: Google API key pattern matched |
18 credential-shaped strings exist in the history
adequateMatches for Google API key, JWT were committed at some point across 1,848 commits examined. Some are still in the working tree. What matters is whether each was rotated after it was committed. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when.
| 5 cited: Google API key pattern added here |
Observability & Operations
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.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on enatega/food-delivery-multivendor: 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.