Read 2026-10-28
moonshine-software/moonshine: technical due diligence, read from its repository
What Borehole read in moonshine-software/moonshine's code and history at 2485e44: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate55% of commit subjects are exact repeats of another subject, and subject length varies by only 15.2 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 731× 'Fix styling' |
| 550× 'Build assets' |
| 404× '[rector] Rector fixes' |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate184 test files against 2,186 source files (8.4%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 184 test files / 2,186 source files |
Product & Engineering Maturity
adequate9% of bug fixes add or change a test
adequateOf 1058 fixes in the last 24 months, 97 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 97 of 1058 |
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 2,364 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/analyse.yml:24 — action pinned by tag |
.github/workflows/lint.yml:24 — action pinned by tag |
5 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-03. 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 4 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 4.20.0. Answer lives in: the release you run, set against each fixed version.
| 2026-09-03: GHSA-54q6-6rhc-7gc4 (high), fixed in 3.18.1: File extension allowlist bypass when preserving or customizing uploaded filenames |
| 2025-08-19: CVE-2025-51487 (moderate): A Stored Cross-Site Scripting (XSS) vulnerability exists in MoonShine version < 3.12.5, allowing to execute arbitrary JavaScript by using "javascript:" payload, |
| 2025-08-19: CVE-2025-51488 (moderate): A Stored Cross-Site Scripting (XSS) vulnerability exists in MoonShine version < 3.12.4, allowing remote attackers to store and execute arbitrary JavaScript by i |
| 2025-08-19: CVE-2025-51489 (moderate): A Stored Cross-Site Scripting (XSS) vulnerability exists in MoonShine version < 3.12.5, allowing remote attackers to upload a malicious SVG file when creating/u |
| 2025-08-19: CVE-2025-51510 (moderate): MoonShine was discovered to contain a SQL injection vulnerability under the Blog -> Categories page when using the moonshine-tree-resource (version < 2.0.2) com |
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 moonshine-software/moonshine: 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.