Read 2026-10-04
rstudio/shiny: technical due diligence, read from its repository
What Borehole read in rstudio/shiny's code and history at 8184460: 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
LICENSE: Relicensed: GPL-3.0 → MIT (2025-12-16)
Architecture & Codebase — including AI provenance
stronginst/www/shared/jqueryui/jquery-ui.js is 18,809 lines, 324× this codebase's median file
adequateThe median source file here is 58 lines. 16 files exceed 1,000 lines, the largest being 18,809. 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.
inst/www/shared/jqueryui/jquery-ui.js:1 — 18,809 lines (324× median) |
inst/www/shared/legacy/jquery.js:1 — 11,009 lines (189× median) |
inst/www/shared/jquery.js:1 — 10,717 lines (184× median) |
inst/www/shared/shiny.js:1 — 7,756 lines (133× median) |
inst/www/shared/selectize/js/selectize.js:1 — 3,487 lines (60× median) |
Engineering Process & SDLC Maturity
strongNo finding.
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 998 tracked files; 0 present |
The build runs third-party code it does not pin
adequate3 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/R-CMD-check.yaml:17 — action pinned by tag |
.github/workflows/R-CMD-check.yaml:19 — action pinned by tag |
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 rstudio/shiny: 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.