Read 2026-11-03
teamwiseflow/xiaobei: technical due diligence, read from its repository
What Borehole read in teamwiseflow/xiaobei's code and history at 47aea0b: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE:1: The licence is MIT with a commercial-licence condition: source available, not open sourceLICENSE: Relicensed: Apache-2.0 → Apache-2.0 with a commercial-licence condition (2025-09-10) → MIT with a commercial-licence condition (2026-04-02)
Architecture & Codebase — including AI provenance
strongcrews/main/skills/_shared/xhs_utils/live.py is 1,510 lines, 18× this codebase's median file
adequateThe median source file here is 82 lines. 2 files exceed 1,000 lines, the largest being 1,510. 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.
crews/main/skills/_shared/xhs_utils/live.py:1 — 1,510 lines (18× median) |
crews/main/skills/_shared/xhs_utils/xhs_pc/api.py:1 — 1,450 lines (17× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate1 test files against 170 source files (0.6%). 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.
| 1 test files / 170 source files |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 913 tracked files |
9% of recent commits change more than 2,000 lines
adequate65 of 715 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.
| 65 commits over 2,000 lines |
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.46 to 1.03 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.46, second half 1.03 (split 2025-07-19) |
8% of bug fixes add or change a test
adequateOf 222 fixes in the last 24 months, 18 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.
| 18 of 222 |
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 913 tracked files; 0 present |
1 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 |
The build runs third-party code it does not pin
adequate1 third-party CI action is referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 5 steps pipe a download straight into a shell. 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/build-dist.yml:48 — action pinned by tag |
scripts/install-atomgit.sh:1549 — download piped into a shell |
The licence is MIT with a commercial-licence condition: source available, not open source
adequateLICENSE grants MIT with a commercial-licence condition: source available, not open source; some uses need a commercial licence from the licensor. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE:1 — 30 lines, MIT AND LicenseRef-Terms-CommercialLicence |
Relicensed: Apache-2.0 → Apache-2.0 with a commercial-licence condition (2025-09-10) → MIT with a commercial-licence condition (2026-04-02)
adequateThe root licence changed 2 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-04. 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.8.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names xiaobei with nothing tying it to this repository (CVE-2025-63258).
| 2026-09-04: CVE-2026-85667 (critical): xiaobei through 5.5.2 fails to implement authentication or signature validation on webhook endpoints, allowing unauthenticated attackers to inject arbitrary mes |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 836 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 836 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 836 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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on teamwiseflow/xiaobei: 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.