Read 2026-10-23
angular/angularfire: technical due diligence, read from its repository
What Borehole read in angular/angularfire's code and history at 29ca012: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongsrc/schematics/update/v21/vertexai-to-ai.jasmine.ts is 1,277 lines, 31× this codebase's median file
adequateThe median source file here is 41 lines. 1 file exceed 1,000 lines, the largest being 1,277. 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.
src/schematics/update/v21/vertexai-to-ai.jasmine.ts:1 — 1,277 lines (31× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate5% of bug fixes add or change a test
adequateOf 38 fixes in the last 24 months, 2 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 2 of 38 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 20.1.1, is not on the branch this survey read; the newest release on it is 20.0.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 20.1.1 |
Security & Reliability Posture
adequate3 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings 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.
| 3 cited: Google API key, where fakes are usual |
3 locked dependencies have published vulnerabilities, 1 high or critical in what ships
adequate3 of 457 locked dependencies match 4 published advisories in OSV, 1 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.
package-lock.json — @grpc/grpc-js 1.9.16: GHSA-m9gg-hp2v-232j (high), fixed in 1.13.6 |
package-lock.json — esbuild 0.24.2: GHSA-67mh-4wv8-2f99 (moderate), fixed in 0.25.0 |
package-lock.json — uuid 9.0.1: GHSA-w5hq-g745-h8pq (moderate), fixed in 11.1.1 |
Observability & Operations
not assessableNot 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 assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on angular/angularfire: 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.