Borehole · Project · free tier
google/guava
Free reading: not for reliance
4d41665 · 7,527 commits · 3,363 files
Read 2026-10-04

google/guava: technical due diligence, read from its repository

What Borehole read in google/guava's code and history at 4d41665: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturitystrong
Security & Reliability Posturestrong
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • CONTRIBUTING.md:8: This repository is a mirror; development happens elsewhere
  • Releases are cut from another branch than the one surveyed
  • README.md:5: names OpenSSF

Architecture & Codebase — including AI provenance

strong
01.6

guava/src/com/google/common/cache/LocalCache.java is 4,997 lines, 40× this codebase's median file

adequate

The median source file here is 123 lines. 40 files exceed 1,230 lines, the largest being 4,997. 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.

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, v33.7.2, is not on the branch this survey read; the newest release on it is v7.0. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag v33.7.2

Security & Reliability Posture

strong
05.65

1 advisory against this project in the last 24 months

adequate

The newest was published on 2026-09-29. 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 1 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 7.0.0. Answer lives in: the release you run, set against each fixed version.

Evidence
2026-09-29: GHSA-xxph-c9ww-hj94 (moderate), fixed in 33.7.2: CompactHashMap/CompactHashSet/MapMakerInternalMap deserialization triggers uncontrolled memory allocation

Observability & Operations

not assessable

Not 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on google/guava: 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.