Read 2026-11-03
firecmsco/firecms: technical due diligence, read from its repository
What Borehole read in firecmsco/firecms's code and history at b0e474d: 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 BUSL-1.1: source available, not open sourceLICENSE: Relicensed: GPL-3.0 → MIT (2021-06-02) → BUSL-1.1 (2024-04-15)
Architecture & Codebase — including AI provenance
strongpackages/ui/src/icons/generated_icons.ts is 2,208 lines, 64× this codebase's median file
adequateThe median source file here is 34 lines. 8 files exceed 1,000 lines, the largest being 2,208. 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.
packages/ui/src/icons/generated_icons.ts:1 — 2,208 lines (64× median) |
packages/ui/src/icons/icon_keys.ts:1 — 2,203 lines (64× median) |
packages/firecms_core/src/util/icon_synonyms.ts:1 — 1,854 lines (54× median) |
packages/firebase_admin/src/DocumentTable.tsx:1 — 1,400 lines (41× median) |
packages/firecms_core/src/types/properties.ts:1 — 1,310 lines (38× median) |
Engineering Process & SDLC Maturity
adequate8% of recent commits change more than 2,000 lines
adequate94 of 1168 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.
| 94 commits over 2,000 lines |
Product & Engineering Maturity
adequateFixes are 55% of recent work, up from 16%
adequateIn the last two quarters 55% of commits were fixes, against 16% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 61%, 48%, 17%, 15%, 12%, 17%, 21%, 12% |
Security & Reliability Posture
adequate12 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key. 1 other match set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| 5 cited: Google API key, where fakes are usual |
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.
discord-bot/Dockerfile — runs as root |
3 environment files are committed
adequatepackages/cli/templates/template_astro/.env, packages/cli/templates/template_next_pro/.env, packages/cli/templates/template_pro/.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.
packages/cli/templates/template_astro/.env — committed environment file |
packages/cli/templates/template_next_pro/.env — committed environment file |
packages/cli/templates/template_pro/.env — committed environment file |
60 locked dependencies have published vulnerabilities, 32 high or critical in what ships
adequate60 of 2,944 locked dependencies match 152 published advisories in OSV, 66 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 — dompurify 3.4.13: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
demo_backend/functions/package-lock.json — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
pnpm-lock.yaml — astro 5.18.2: GHSA-26w7-cxv4-gfx2 (critical), fixed in 7.2.8; a development dependency |
12 places insert HTML from a variable without sanitising it
adequate12 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.
packages/cli/templates/template_astro/src/blog/BlogPost.tsx:79 — HTML from a variable |
packages/datatalk/src/components/CodeBlock.tsx:23 — HTML from a variable |
packages/datatalk/src/components/SystemMessage.tsx:73 — HTML from a variable |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
packages/cli/templates/template/vite.config.ts:12 — source maps in a production build |
packages/cli/templates/template_pro/vite.config.ts:12 — source maps in a production build |
packages/cli/vite.config.ts:26 — source maps in a production build |
The licence is BUSL-1.1: source available, not open source
adequateLICENSE grants BUSL-1.1: source available, not open source; production use restricted until the change date. 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 — 6 lines, BUSL-1.1 |
Relicensed: GPL-3.0 → MIT (2021-06-02) → BUSL-1.1 (2024-04-15)
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.
Observability & Operations
adequateNo 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 3,421 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 |
The code branches on the environment's name at 12 places
adequate12 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.
packages/cli/src/cli.ts:91 — branch on the environment name |
packages/cli/src/cli.ts:108 — branch on the environment name |
packages/cli/src/cli.ts:132 — branch on the environment name |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on firecmsco/firecms: 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.