Read 2026-10-23
rjsf-team/react-jsonschema-form: technical due diligence, read from its repository
What Borehole read in rjsf-team/react-jsonschema-form's code and history at 14cab6f: 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 | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongpackages/core/src/components/Form.tsx is 1,655 lines, 48× this codebase's median file
adequateThe median source file here is 34 lines. 4 files exceed 1,000 lines, the largest being 1,655. 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/components/Form.tsx:1 — 1,655 lines (48× median) |
packages/utils/src/types.ts:1 — 1,545 lines (45× median) |
packages/utils/src/schema/retrieveSchema.ts:1 — 1,201 lines (35× median) |
packages/core/src/components/fields/ArrayField.tsx:1 — 1,118 lines (32× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v6.11.0, is not on the branch this survey read; the newest release on it is 6.2.2. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v6.11.0 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate6 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/change-tag-name.yml:13 — action pinned by tag |
.github/workflows/ci.yml:18 — action pinned by tag |
13 locked dependencies have published vulnerabilities, 7 high or critical in what ships
adequate13 of 1,964 locked dependencies match 42 published advisories in OSV, 28 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.16: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17; a development dependency |
pnpm-lock.yaml — tinypool 1.1.1: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1; a development dependency |
pnpm-lock.yaml — tinypool 2.1.0: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1; a development dependency |
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 rjsf-team/react-jsonschema-form: 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.