Read 2026-10-23
decaporg/decap-cms: technical due diligence, read from its repository
What Borehole read in decaporg/decap-cms's code and history at 9d1bb3b: 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 | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongpackages/decap-cms-backend-github/src/API.ts is 2,001 lines, 28× this codebase's median file
adequateThe median source file here is 71 lines. 5 files exceed 1,000 lines, the largest being 2,001. 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/decap-cms-backend-github/src/API.ts:1 — 2,001 lines (28× median) |
packages/decap-cms-core/src/backend.ts:1 — 1,726 lines (24× median) |
packages/decap-cms-core/src/actions/entries.ts:1 — 1,560 lines (21× median) |
packages/decap-cms-backend-forgejo/src/API.ts:1 — 1,062 lines (14× median) |
packages/decap-cms-backend-gitlab/src/API.ts:1 — 1,043 lines (14× median) |
A move from JavaScript to TypeScript began 83 months ago and is 31% done
adequate163 product files are in the new language and 365 are still in the old one, 83 months after the first new file appeared. The new language's share of the lines rose from 0% to 48%, and moved 7 percentage points in the last year. Two languages for one job doubles what an engineer has to know, and the unmoved half is usually what nobody wants to touch. Ask whether finishing it is planned, and what it costs.
| 365 old, 163 new |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate14 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. 9 other matchs 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: AWS access key, where fakes are usual |
The build runs third-party code it does not pin
adequate5 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.
.github/workflows/labeler.yml:11 — action pinned by tag |
.github/workflows/nodejs.yml:22 — action pinned by tag |
41 locked dependencies have published vulnerabilities, 23 high or critical in what ships
adequate41 of 2,500 locked dependencies match 112 published advisories in OSV, 47 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 — tar 7.5.11: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
pnpm-lock.yaml — babel-traverse 6.26.0: GHSA-67hx-6x53-jw92 (critical); a development dependency |
pnpm-lock.yaml — form-data 2.3.3: GHSA-fjxv-7rqg-78g4 (critical), fixed in 2.5.4; a development dependency |
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/decap/webpack.config.cjs:25 — source maps in a production build |
3 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-01. 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 3.17.1. Answer lives in: the release you run, set against each fixed version.
| 2026-09-01: GHSA-jm5q-pq3r-26g9 (low), fixed in 3.3.0: Bitbucket OAuth refresh token exposed in request URL |
| 2026-09-01: GHSA-5rrq-v82w-qpfr (critical), fixed in 3.11.0: decap-server local_git path traversal via prefix-based repository boundary check allows out-of-repository read, write, and delete |
| 2025-09-10: CVE-2025-57520 (moderate): A Cross Site Scripting (XSS) vulnerability exists in Decap CMS thru 3.8.3. Input fields such as body, tags, title, and description are not properly sanitized be |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,180 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 1,180 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 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 decaporg/decap-cms: 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.