growilabs/growi: technical due diligence, read from its repository

32% of commit subjects are exact repeats of another subject, and subject length varies by only 23.9 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. This was read from the most recent 50,000 commits (30 Oct 2020 to 2 Nov 2026) only; older history was not read.

The median source file here is 73 lines. 27 files exceed 1,000 lines, the largest being 5,808. 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.

Of 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.

The suite is configured to retry failing tests (apps/app/playwright.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.

apps/app/.env.production, apps/pdf-converter/.env, apps/slackbot-proxy/.env are tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.

30 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.

1 places read data with a deserialiser that executes what it reads (PHP `unserialize`). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.

178 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.

The newest was published on 2026-10-28. 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 3 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 8.0.8. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 52 records name growi with nothing tying them to this repository (CVE-2018-0652, CVE-2018-0653, CVE-2018-0654, …).

Nothing 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.

19 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.