architect/architect: technical due diligence, read from its repository

What Borehole read in architect/architect's code and history at 9924cd0: 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	adequate
Product & Engineering Maturity	not assessable
Security & Reliability Posture	strong
Observability & Operations	not assessable
Fit with the Acquirer	not assessable

Architecture & Codebase — including AI provenance

strong

No finding.

Engineering Process & SDLC Maturity

adequate

02.5

35% of commit subjects say nothing about the change

adequate

722 of 2,064 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.

Evidence

722/2,064 low-content subjects (35.0%)

'hbd'

'rename'

'1.0.1'

'1.0.2'

Product & Engineering Maturity

not assessable

Not rated: only 9 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Security & Reliability Posture

strong

05.3

5 dependencies float, and no lockfile is committed

adequate

Dependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.

Evidence

package.json:19 — >=22

package.json:36 — ~6.1.0

package.json:39 — ~6.0.0

package.json:40 — ^0.23.2

package.json:48 — ~2.1.3