Borehole · Project · free tier
kludex/starlette
Free reading: not for reliance
2284ff0 · 1,751 commits · 150 files
Read 2026-10-04

kludex/starlette: technical due diligence, read from its repository

What Borehole read in kludex/starlette's code and history at 2284ff0: 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

  • AI_POLICY.md:1: states a policy on AI-generated contributions

Architecture & Codebase — including AI provenance

strong

No finding.

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong
04.5

Effort is shifting from building to rewriting

adequate

Deleted lines per line added rose from 0.51 to 0.84 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.

Evidence
first half 0.51, second half 0.84 (split 2022-08-11)

Security & Reliability Posture

strong
05.26

3 locked dependencies have published vulnerabilities, 3 high or critical

adequate

3 of 88 locked dependencies match 5 published advisories in OSV, 3 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. None of the high or critical ones is in what the product ships: they are development dependencies.

Evidence
uv.lock — jaraco-context 6.0.1: GHSA-58pv-8j8x-9vj2 (high), fixed in 6.1.0; a development dependency
uv.lock — urllib3 2.7.0: GHSA-8988-9cw3-xx77 (high), fixed in 2.8.0; a development dependency
uv.lock — click 8.2.1: PYSEC-2026-2132 (unrated), fixed in 8.3.3; a development dependency
05.65

8 advisories against this project in the last 24 months, 4 high or critical, 1 on CISA's known-exploited list

adequate

1 of them is on CISA's known-exploited list: check first whether the release you run has the fix. The newest was published on 2026-06-12. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 12 records name starlette with nothing tying them to this repository (CVE-2023-29159, CVE-2023-30798, CVE-2024-47874, …).

Evidence
2026-05-21: GHSA-86qp-5c8j-p5mr (moderate; on CISA's Known Exploited list), fixed in 1.0.1: Starlette has missing Host header validation that poisons request.url.path, bypassing path-based security checks
2026-06-12: GHSA-82w8-qh3p-5jfq (high), fixed in 1.3.1: Starlette: request.form() limits silently ignored for application/x-www-form-urlencoded enable DoS
2026-06-11: GHSA-jp82-jpqv-5vv3 (low), fixed in 1.3.0: Starlette: Unvalidated request path concatenated into authority poisons request.url.hostname
2026-05-23: GHSA-wqp7-x3pw-xc5r (high), fixed in 1.1.0: Starlette: SSRF and NTLM credential theft via UNC paths in StaticFiles on Windows
2026-05-23: GHSA-x746-7m8f-x49c (moderate), fixed in 1.1.0: Starlette: Arbitrary HTTP method dispatched to `HTTPEndpoint` attributes via `getattr`

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 kludex/starlette: 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.