Borehole · Project · free tier
qax-os/excelize
Free reading: not for reliance
611b222 · 1,470 commits · 125 files
Read 2026-10-23

qax-os/excelize: technical due diligence, read from its repository

What Borehole read in qax-os/excelize's code and history at 611b222: 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 Postureadequate
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • LICENSE.md: Relicensed: BSD-3-Clause → BSD-3-Clause AND proprietary (2018-01-03) → BSD-3-Clause (2020-03-29)
  • .github/CONTRIBUTING.md:54: states a policy on AI-generated contributions
  • .github/CONTRIBUTING.md:227: names Linux Foundation

Architecture & Codebase — including AI provenance

strong
01.6

calc.go is 19,693 lines, 45× this codebase's median file

adequate

The median source file here is 434 lines. 2 files exceed 4,340 lines, the largest being 19,693. 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.

Evidence
calc.go:1 — 19,693 lines (45× median)
numfmt.go:1 — 7,927 lines (18× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong

No finding.

Security & Reliability Posture

adequate
05.60

Relicensed: BSD-3-Clause → BSD-3-Clause AND proprietary (2018-01-03) → BSD-3-Clause (2020-03-29)

adequate

The root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

Evidence
LICENSE.md — BSD-3-Clause from 2016-08-31
LICENSE — BSD-3-Clause AND proprietary from 2018-01-03
LICENSE — BSD-3-Clause from 2020-03-29
05.65

19 advisories against this project in the last 24 months, 12 high or critical, 15 fixed in no release yet

adequate

The newest was published on 2026-10-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. GHSA-mx22-3794-2vpv (high), GHSA-jw42-f3rr-4cc3 (high), GHSA-r7x5-4969-99p7 (high) and 12 more affect 2.11.0, the newest release, and not the surveyed commit: their fixes are in the surveyed commit and in no release. Answer lives in: the version you run.

Evidence
2026-10-03: GHSA-mx22-3794-2vpv (high), fixed in the surveyed commit and in no release: Excelize: Unchecked pivot-cache field index in extractPivotTableFields causes unrecoverable panic
2026-09-30: GHSA-jw42-f3rr-4cc3 (high), fixed in the surveyed commit and in no release: Excelize: Unbounded row number in Rows.Columns makes GetRows and the Rows iterator loop for days
2026-09-29: GHSA-r7x5-4969-99p7 (high), fixed in the surveyed commit and in no release: Excelize: Nil-pointer dereference in GetSlicers when a worksheet has extLst present but no drawing element
2026-09-15: GHSA-2j4c-ffch-9f23 (high), fixed in the surveyed commit and in no release: Excelize Decrypt: unrecoverable panics on malformed OLE/CFB encrypted workbooks
2026-09-12: GHSA-x2q3-8cjh-766f (high), fixed in the surveyed commit and in no release: Excelize: extractPart allocates attacker-controlled, unbounded and negative-sized buffers from CFB directory entries: remote panic / OOM DoS

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 qax-os/excelize: 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.