Read 2026-11-07
ceuilisa/pixiv-shaft: technical due diligence, read from its repository
What Borehole read in ceuilisa/pixiv-shaft's code and history at d958950: 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
LICENSE: Relicensed: MIT → GPL-2.0 (2026-08-10)
Architecture & Codebase — including AI provenance
strongapp/src/main/java/ceui/lisa/utils/Settings.java is 2,258 lines, 22× this codebase's median file
adequateThe median source file here is 102 lines. 15 files exceed 1,020 lines, the largest being 2,258. 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.
app/src/main/java/ceui/lisa/utils/Settings.java:1 — 2,258 lines (22× median) |
app/src/main/java/ceui/pixiv/ui/debug/NetworkTestViewModel.kt:1 — 2,163 lines (21× median) |
app/src/main/java/ceui/lisa/core/Manager.java:1 — 1,958 lines (19× median) |
app/src/main/java/ceui/pixiv/ui/detail/ArtworkV3Fragment.kt:1 — 1,807 lines (17× median) |
app/src/main/java/ceui/pixiv/ui/novel/reader/NovelReaderV3Fragment.kt:1 — 1,779 lines (17× median) |
Engineering Process & SDLC Maturity
strongAlmost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 3,341 tracked files |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v5.0.24, is not on the branch this survey read; the newest release on it is v4.9.8. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v5.0.24 |
Security & Reliability Posture
adequate9 credential-shaped strings committed to the tree
adequateMatches for Google API key appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when. Only Google API keys matched. Those are often public by design, in a browser app's Firebase or Maps configuration; the question is whether each is restricted to the app's domains and APIs.
| 5 cited: Google API key pattern matched |
None 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 3,341 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/gradle.yml:52 — action pinned by tag |
.github/workflows/gradle.yml:312 — action pinned by tag |
1 locked dependency has published vulnerabilities, 1 high or critical
adequate1 of 78 locked dependencies match 2 published advisories in OSV, 1 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
gradle/libs.versions.toml — org.jsoup:jsoup 1.18.1: GHSA-65r4-943x-97jj (high), fixed in 1.23.2 |
The app allows plain HTTP to any server
adequateThe app's manifest allows unencrypted HTTP app-wide (NSAllowsArbitraryLoads, or cleartext traffic permitted), rather than for named domains. Anything sent over plain HTTP can be read on the network, and enterprise security reviews ask about it. Some apps need it by nature (a podcast or feed reader fetches whatever URL a feed gives), so ask which case this is.
app/src/main/res/xml/network_security_config.xml:3 — cleartext allowed app-wide |
Relicensed: MIT → GPL-2.0 (2026-08-10)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
Observability & Operations
not assessableNot rated: only 6 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 ceuilisa/pixiv-shaft: 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.