Read 2026-10-23
gitcoffee-os/postbot: technical due diligence, read from its repository
What Borehole read in gitcoffee-os/postbot's code and history at 5d48182: 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 | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: Apache-2.0 → Apache-2.0 with a commercial-licence condition (2025-06-09) → Apache-2.0 (2025-06-09)
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate51% of commit subjects are exact repeats of another subject, and subject length varies by only 9.5 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.
| 31× '更新 README.md' |
| 9× 'Update README.md' |
| 5× 'Update LICENSE' |
Engineering Process & SDLC Maturity
adequateTests are absent or token
adequate0 test files against 105 source files (0.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.
| 0 test files / 105 source files |
Nothing in the history is tagged as a release
adequateAcross 1.4 years of history there is not one tag. There may still be a deployment process, but this repository holds no record of what shipped when — which is the record a buyer needs to reconstruct an incident or a regression after the fact.
| 0 tags across 104 commits and 511 days |
26% of commit subjects say nothing about the change
adequate27 of 103 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
| 27/103 low-content subjects (26.2%) |
| 'v1.0.0 代码提交' |
| '更新 LICENSE' |
| '优化细节' |
| '更新 README' |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — none are present. 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.
| 0 of 5 markers present across 123 tracked files |
Product & Engineering Maturity
not assessableChange keeps returning to the same few files
adequateFive files out of 166 absorb 27% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
README.md — 78 commits touched it |
package.json — 40 commits touched it |
src/media/publisher/publisher.script.ts — 21 commits touched it |
src/media/platform/index.ts — 19 commits touched it |
src/contents/index.ts — 11 commits touched it |
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 123 tracked files; 0 present |
29 locked dependencies have published vulnerabilities, 32 high or critical in what ships
adequate29 of 667 locked dependencies match 59 published advisories in OSV, 32 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.
pnpm-lock.yaml — @vue/server-renderer 3.3.4: GHSA-g2v6-rqmx-r4w6 (high), fixed in 3.5.42 |
pnpm-lock.yaml — @vue/server-renderer 3.4.19: GHSA-g2v6-rqmx-r4w6 (high), fixed in 3.5.42 |
pnpm-lock.yaml — browserslist 4.22.1: GHSA-73wf-gq98-2v4g (high), fixed in 4.28.7 |
23 places insert HTML from a variable without sanitising it
adequate23 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
src/contents/index.ts:125 — HTML from a variable |
src/media/publisher/platform/article/baijiahao.publisher.ts:177 — HTML from a variable |
src/media/publisher/platform/article/bilibili.publisher.ts:141 — HTML from a variable |
Relicensed: Apache-2.0 → Apache-2.0 with a commercial-licence condition (2025-06-09) → Apache-2.0 (2025-06-09)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
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 gitcoffee-os/postbot: 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.