Read 2026-10-28
eclipsesource/jsonforms: technical due diligence, read from its repository
What Borehole read in eclipsesource/jsonforms's code and history at 2c5fae6: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:44: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongpackages/core/src/mappers/renderer.ts is 1,421 lines, 19× this codebase's median file
adequateThe median source file here is 72 lines. 1 file exceed 1,000 lines, the largest being 1,421. 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/core/src/mappers/renderer.ts:1 — 1,421 lines (19× median) |
Engineering Process & SDLC Maturity
adequate21 tests are switched off
adequate21 skip markers across 15 of 184 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.
packages/angular-material/test/categorization-tab-layout.spec.ts:293 — skipped test |
packages/angular-material/test/common/range.ts:313 — skipped test |
packages/angular-material/test/common/text.ts:418 — skipped test |
Product & Engineering Maturity
strongNo finding.
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 845 tracked files; 0 present |
94 locked dependencies have published vulnerabilities, 128 high or critical
adequate94 of 2,867 locked dependencies match 204 published advisories in OSV, 128 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. None of the high or critical ones is in what the product ships: they are development dependencies.
pnpm-lock.yaml — piscina 5.1.3: GHSA-67c8-pqhq-4rmx (critical), fixed in 5.3.2; a development dependency |
pnpm-lock.yaml — piscina 5.1.4: GHSA-67c8-pqhq-4rmx (critical), fixed in 5.3.2; a development dependency |
pnpm-lock.yaml — sha.js 2.4.11: GHSA-95m3-7q98-8xr5 (critical), fixed in 2.4.12; 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/core/rollup.config.js:18 — source maps in a production build |
packages/material-renderers/rollup.config.js:25 — source maps in a production build |
packages/react/rollup.config.js:35 — source maps in a production build |
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 eclipsesource/jsonforms: 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.