Read 2026-10-23
apereo/cas: technical due diligence, read from its repository
What Borehole read in apereo/cas's code and history at 5cd5135: 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
strongCommit messages are templated rather than written
adequate51% of commit subjects are exact repeats of another subject, and subject length varies by only 26.5 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.
| 1380× 'fix tests' |
| 640× 'doc updates' |
| 321× 'add tests' |
support/cas-server-support-thymeleaf/src/main/resources/static/js/palantir-services-wizard.js is 4,083 lines, 75× this codebase's median file
adequateThe median source file here is 54 lines. 16 files exceed 1,000 lines, the largest being 4,083. 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.
support/cas-server-support-thymeleaf/src/main/resources/static/js/palantir-services-wizard.js:1 — 4,083 lines (75× median) |
support/cas-server-support-thymeleaf/src/main/resources/static/js/palantir-system.js:1 — 2,770 lines (51× median) |
api/cas-server-core-api-webflow/src/main/java/org/apereo/cas/web/flow/CasWebflowConstants.java:1 — 2,407 lines (44× median) |
core/cas-server-core-web-api/src/main/java/org/apereo/cas/web/support/WebUtils.java:1 — 2,024 lines (37× median) |
support/cas-server-support-oauth/src/main/java/org/apereo/cas/config/CasOAuth20Configuration.java:1 — 1,930 lines (35× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequate157 tests are individually marked to retry. A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v8.0.2, is not on the branch this survey read; the newest release on it is v3.5.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v8.0.2 |
Security & Reliability Posture
adequate36 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 5 cited: AWS access key, where fakes are usual |
The build runs third-party code it does not pin
adequate10 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/analysis.yml:55 — action pinned by tag |
.github/workflows/analysis.yml:194 — action pinned by tag |
4 deserialisers that can run code
adequate4 places read data with a deserialiser that executes what it reads (Java object streams). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
core/cas-server-core-util-api/src/main/java/org/apereo/cas/util/serialization/SerializationUtils.java:96 — code-executing deserialiser |
core/cas-server-core-webflow-api/src/main/java/org/apereo/cas/web/flow/executor/EncryptedTranscoder.java:65 — code-executing deserialiser |
core/cas-server-core-webflow-api/src/main/java/org/apereo/cas/web/flow/executor/EncryptedTranscoder.java:66 — code-executing deserialiser |
1 locked dependency has published vulnerabilities, 2 high or critical
adequate1 of 536 locked dependencies match 2 published advisories in OSV, 2 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.codehaus.jackson:jackson-mapper-asl 1.9.13: GHSA-c27h-mcmw-48hv (critical) |
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 apereo/cas: 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.