Read 2026-10-23
usememos/memos: technical due diligence, read from its repository
What Borehole read in usememos/memos's code and history at 28719a9: 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 | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongmarkdown/parser/tag_unicode_tables.go is 5,122 lines, 50× this codebase's median file
adequateThe median source file here is 102 lines. 5 files exceed 1,020 lines, the largest being 5,122. 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.
markdown/parser/tag_unicode_tables.go:1 — 5,122 lines (50× median) |
web/src/types/proto/api/user_service_pb.ts:1 — 3,152 lines (30× median) |
web/src/types/proto/api/memo_service_pb.ts:1 — 1,590 lines (15× median) |
web/src/types/proto/api/instance_service_pb.ts:1 — 1,490 lines (14× median) |
filter/parser.go:1 — 1,033 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate11 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; 2 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/backend-tests.yml:46 — action pinned by tag |
.github/workflows/backend-tests.yml:94 — action pinned by tag |
scripts/install.sh:27 — download piped into a shell |
23 SQL statements built from strings
adequate23 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 22 of them a value, not a table or column name, goes into the string. Where any of those values comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
store/db/mysql/attachment.go:63 — SQL built from a string |
store/db/mysql/idp.go:18 — SQL built from a string |
store/db/mysql/idp.go:121 — SQL built from a string |
14 locked dependencies have published vulnerabilities, 1 high or critical in what ships
adequate14 of 515 locked dependencies match 50 published advisories in OSV, 17 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.
web/pnpm-lock.yaml — react-router 7.15.0: GHSA-chx6-hx7r-mcp5 (high), fixed in 7.18.0 |
web/pnpm-lock.yaml — browserslist 4.28.2: GHSA-73wf-gq98-2v4g (high), fixed in 4.28.7; a development dependency |
web/pnpm-lock.yaml — nanoid 3.3.11: GHSA-28wg-ghj8-5hjv (high), fixed in 3.3.16; a development dependency |
18 advisories against this project in the last 24 months, 5 high or critical
adequateThe newest was published on 2026-10-20. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. The record is incomplete: NVD: 4 records name memos with nothing tying them to this repository (CVE-2025-58242, CVE-2026-108727, CVE-2026-72803, …).
| 2026-10-20: CVE-2026-113601 (moderate): Memos before 0.27.0 contains a missing authorization vulnerability in the ActivityService ListActivities and GetActivity API methods that allows authenticated u |
| 2026-09-01: CVE-2026-84203 (high): Memos versions 0.26.0 through 0.30.0 fail to revoke refresh tokens when a user changes their password, allowing attackers to maintain account access. An attacke |
| 2026-08-29: CVE-2026-82476 (moderate): Memos through 0.30.0 omits the 100.64.0.0/10 carrier-grade NAT address range from SSRF protection in its link-metadata fetcher, allowing unauthenticated attacke |
| 2026-08-05: CVE-2026-71271 (high): Memos' webhook URL validation, isReservedIP (internal/webhook/validate.go), checks a candidate IP against a reservedCIDRs list that omits 0.0.0.0/8 and never ca |
| 2026-08-05: CVE-2026-71272 (high): Memos' webhook dispatch function safeDialContext (internal/webhook/webhook.go) resolves the target hostname via net.DefaultResolver.LookupHost and validates the |
Observability & Operations
strongNo 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 usememos/memos: 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.