Read 2026-11-03
attify/firmware-analysis-toolkit: technical due diligence, read from its repository
What Borehole read in attify/firmware-analysis-toolkit's code and history at 54dd1a2: 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 | strong |
| Product & Engineering Maturity | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE:1: The licence is FSL-1.1-ALv2: source available, not open sourceLICENSE: Relicensed: MIT → FSL-1.1-ALv2 (2026-09-08)
Architecture & Codebase — including AI provenance
strongcrates/fat_cli/src/emulate_cmd.rs is 8,825 lines, 45× this codebase's median file
adequateThe median source file here is 195 lines. 10 files exceed 1,950 lines, the largest being 8,825. 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.
crates/fat_cli/src/emulate_cmd.rs:1 — 8,825 lines (45× median) |
crates/fat_cli/src/main.rs:1 — 6,995 lines (35× median) |
crates/fat_query/src/android/extractor.rs:1 — 3,829 lines (19× median) |
crates/fat_cli/src/helptext.rs:1 — 3,337 lines (17× median) |
crates/fat_cli/src/crypto_cmd.rs:1 — 2,796 lines (14× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
not assessableNot rated: only 8 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate2 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 2 steps pipe a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/release.yml:140 — action pinned by tag |
.github/workflows/release.yml:148 — action pinned by tag |
.github/workflows/release.yml:71 — download piped into a shell |
6 locked dependencies have published vulnerabilities, 2 high or critical
adequate6 of 212 locked dependencies match 22 published advisories in OSV, 2 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
Cargo.lock — zip 2.4.2: GHSA-m665-v7pm-7grj (critical), fixed in 9.0.5 |
Cargo.lock — number_prefix 0.4.0: RUSTSEC-2025-0119 (unrated) |
Cargo.lock — unsafe-libyaml 0.2.11: RUSTSEC-2024-0449 (unrated) |
The licence is FSL-1.1-ALv2: source available, not open source
adequateLICENSE grants FSL-1.1-ALv2: source available, not open source; a competing commercial product or service is not allowed; each version becomes Apache-2.0 two years after its release. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE:1 — 105 lines, FSL-1.1-ALv2 |
Relicensed: MIT → FSL-1.1-ALv2 (2026-09-08)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
Observability & Operations
not assessableNot rated: only 4 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 assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on attify/firmware-analysis-toolkit: 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.