Borehole · Project · free tier
filosottile/age
Free reading: not for reliance
b74dce4 · 431 commits · 97 files
Read 2026-10-04

filosottile/age: technical due diligence, read from its repository

What Borehole read in filosottile/age's code and history at b74dce4: 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

Architecture & Codebase — including AI provenance

strong

No finding.

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong

No finding.

Security & Reliability Posture

adequate
05.1

5 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings

adequate

Strings 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.

Evidence
5 cited: private key block, where fakes are usual
05.2

None of the standard security guard rails are configured

adequate

There 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.

Evidence
checked 5 kinds of guard rail across 97 tracked files; 0 present
05.26

1 locked dependency has published vulnerabilities

adequate

1 of 9 locked dependencies match 2 published advisories in OSV. 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.

Evidence
go.mod — golang.org/x/crypto v0.55.0: GO-2026-6354 (unrated), fixed in 0.56.0

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 filosottile/age: 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.