Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
builtbybel/FlyOOBE carries serious gaps (44%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
It is strongest in Architecture (100%) — the structure is clean and changes stay contained. Security (92%) is solid too.
The area that most needs attention is Readiness (24%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Maturity (45%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); Run what this repository's stack ships (Security & performance tooling); 1 No automated tests finding(s) in Code Coverage (Code Coverage).
For scale: Small (~8,810 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
Code Health
63%
Adequate
Architecture
100% ★
Exemplary
Maturity
45%
Weak · gated by D34, M2
Readiness
24% ⚠
Critical · gated by D8, D9, P1, P3
Security
92% ★
Exemplary
How the score is built — each lens's share of the headline
Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
Readiness 24% · 47% weightMaturity 45% · 26% weightCode Health 63% · 14% weightSecurity 92% · 8% weightArchitecture 100% · 4% weight
Raise Readiness 24 → 70 (the Healthy floor) ⇒ headline 44 → ~60.
Code composition — where the lines go
Business logic 24%Plumbing 47%Generated 29%
Rebuild cost & value ~ Modeled — €4,400–€22,000
| Cost to rebuild | €4,400–€22,000 |
| Domain complexity | Standard |
| Quality factor | 0.7× (at 44% quality) |
| Size & shape | Small · 30% boilerplate · 36% straight-line · 34% branching logic |
This codebase represents roughly ~0.1 person-years of build effort (about ~€13,000 to rebuild). Its weakest lens is Readiness at 24% — the part of that asset most exposed by the findings below.
Top priorities
1
Resolve the 1 No automated tests finding(s) in Code Coverage.
2
Resolve the 1 No tests found finding(s) in Test Distribution.
3
Add a CI workflow that builds and runs the test suite on every push/PR.
Diagnosis — what's actually going on
Value concentrated against a weak lens
This is a Small asset (~0.1 person-years to rebuild), and its weakest lens is Readiness at 24%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
Highest-leverage move
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Architecture — module dependency matrix
At a glance — Code Health
The Good
D1 · .NET / C#
Cyclomatic Complexity
9.2
D2 · .NET / C#
Cognitive Complexity
8.6
D3 · .NET / C#
God Classes
10.0
D4 · .NET / C#
Code Duplication
9.9
D17 · .NET / C#
Explicit Debt
8.9
D18 · .NET / C#
Solution Shape
10.0
GD1 · Repo
Unfinished & placeholder code
10.0
IC1 · Repo
Incompleteness & stubs
8.9
At a glance — Architecture
The Good
D5 · .NET / C#
Coupling
10.0
D6 · .NET / C#
Cohesion (LCOM4)
10.0
D26 · .NET / C#
Project Cohesion
10.0
D35 · .NET / C#
Change Coupling
10.0
AX10 · Repo
Code composition
10.0
AX3 · Repo
Project dependency cycles
10.0
AX4 · Repo
Dependency direction
10.0
AX5 · Repo
Architecture & structure
10.0
AX6 · Repo
Interface segregation
10.0
At a glance — Maturity
The Good
The Bad
The Ugly
At a glance — Readiness
The Good
The Bad
The Ugly
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2021 — Cryptographic Failures | 2 | High / Critical |
| A03:2021 — Injection | 1 | Medium |
Roadmap
First, establish a CI/CD pipeline to automatically build the code and run the test suite on every push or pull request. Next, integrate security and performance tooling, such as CodeQL or Semgrep, into this workflow to ensure security regressions fail the build. Then, address the single missing automated test to improve code coverage. After that, ensure all tests are properly detected and distributed. Finally, maintain a changelog to record changes for each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +16.1 pts | Low | Code Coverage |
| Resolve the 1 No tests found finding(s) in Test Distribution. | +16.1 pts | Low | Test Distribution |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +19.3 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +19.3 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +16.1 pts | Medium | Release Hygiene |
| Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. | +6.7 pts | Low | Knowledge Freshness |
| Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability. | +12.3 pts | Medium | Observability |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.6 pts | Low | ADR Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| Flyoobe/InstallView/ToolHelper.cs | 4.2 | Mixed | Explicit Debt: EmptyCatchBlock |
| Flyoobe/InstallView/AdvancedControlView.cs | 6.1 | Mixed | Explicit Debt: EmptyCatchBlock |
| Flyoobe/InstallView/InPlaceRepairProvider.cs | 6.1 | Mixed | Explicit Debt: EmptyCatchBlock |
| docs/update-check.html | 7.2 | Mixed | Secrets (history): Secret: jwt |
| Flyoobe/Helper/BackgroundHelper.cs | 7.3 | Mixed | Cyclomatic Complexity: BackgroundHelper.CreateBrush (cyclomatic 17) |
| Flyoobe/InstallView/BootMenuInfoProvider.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Flyoobe/InstallView/RunSetupFromIsoProvider.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Flyoobe/ToolHubView/ToolHubControlView.cs | 7.8 | Mixed | Cyclomatic Complexity: ToolHubControlView.ReadMetadataFromScript (cyclomatic 22) |
| Flyoobe/ToolHubView/ToolHubItemControl.cs | 7.8 | Mixed | Cyclomatic Complexity: ToolHubItemControl.btnRun_Click (cyclomatic 21) |
| Flyoobe/Views/AiControlView.cs | 7.8 | Mixed | Cyclomatic Complexity: AiControlView.DoRemove (cyclomatic 16) |
| Flyby11-deprecated/Flyby11/IsoHandler.cs | 7.9 | Mixed | Static Analysis (SAST): Medium: unsafe-path-combine |
| Flyoobe/Views/DeviceControlView.cs | 8.5 | Near-clean | Cognitive Complexity: DeviceControlView.btnApply_Click (cognitive 17) |
| Flyoobe/Views/UpdatesControlView.cs | 8.5 | Near-clean | Cognitive Complexity: UpdatesControlView.Install (cognitive 16) |
| Flyoobe/Features/Ads/FinishSetupAds.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 16) |
| Flyoobe/Features/Edge/DefaultTopSites.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 38 of 41 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 41 dimensions across the health lenses
D1D2D3D4D5D6D8D9D12D13D15D16D17D18D19D20D21D24D26D28D29D34D35AX10AX3AX4AX5AX6GD1IC1M1M2M3M4P1P2P3P6X1X2X3
How to trust any code-health report — three questions
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 26 of 36 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| jscpd | Code duplication | — | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.302 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.302 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | Local LLM | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
- D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
Dimensions
D1 · Cyclomatic Complexity
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ToolHubControlView.ReadMetadataFromScript at 22.
ToolHubControlView.ReadMetadataFromScript (cyclomatic 22)Flyoobe/ToolHubView/ToolHubControlView.cs:124
ToolHubItemControl.btnRun_Click (cyclomatic 21)Flyoobe/ToolHubView/ToolHubItemControl.cs:117
BackgroundHelper.CreateBrush (cyclomatic 17)Flyoobe/Helper/BackgroundHelper.cs:188
ToolHelpers.ResolveToolPath (cyclomatic 17)Flyoobe/InstallView/ToolHelper.cs:13
AiControlView.DoRemove (cyclomatic 16)Flyoobe/Views/AiControlView.cs:66
Do you agree with this assessment?
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was ToolHelpers.ResolveToolPath at 32.
ToolHelpers.ResolveToolPath (cognitive 32)Flyoobe/InstallView/ToolHelper.cs:13
ToolHubControlView.ReadMetadataFromScript (cognitive 29)Flyoobe/ToolHubView/ToolHubControlView.cs:124
ToolHubItemControl.btnRun_Click (cognitive 22)Flyoobe/ToolHubView/ToolHubItemControl.cs:117
AiControlView.DoRemove (cognitive 20)Flyoobe/Views/AiControlView.cs:66
AdvancedControlView.RunSelectedAsync (cognitive 20)Flyoobe/InstallView/AdvancedControlView.cs:171
What to do
- Resolve the 1 ToolHelpers.ResolveToolPath (cognitive 32) finding(s) in Cognitive Complexity — start with ToolHelper.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ToolHubControlView.ReadMetadataFromScript (cognitive 29) finding(s) in Cognitive Complexity — start with ToolHubControlView.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ToolHubItemControl.btnRun_Click (cognitive 22) finding(s) in Cognitive Complexity — start with ToolHubItemControl.cs. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Do you agree with this assessment?
D3 · God Classes
0 god class(es) detected.
Do you agree with this assessment?
D4 · Code Duplication
3 duplicated block group(s) detected.
Duplicated block (13 lines × 16)Flyoobe/Features/Ads/FinishSetupAds.cs:33
Duplicated block (13 lines × 2)Flyoobe/Features/Edge/DefaultTopSites.cs:32
Duplicated block (10 lines × 2)Flyoobe/InstallView/InPlaceRepairProvider.cs:44
Do you agree with this assessment?
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
Do you agree with this assessment?
D6 · Cohesion (LCOM4)
0 of 19 classes have LCOM4 above 3.
Do you agree with this assessment?
D8 · Code Coverage
No automated tests — no test code was found in this repository.
No automated tests
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Do you agree with this assessment?
D9 · Test Distribution
No test suite found.
No tests found
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D12 · Dependency Hygiene
0 outdated, 0 vulnerable, 0 deprecated packages.
Do you agree with this assessment?
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
Do you agree with this assessment?
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
Do you agree with this assessment?
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Flyoobe/Helper/DonationHelper.cs.
Off-boarding risk: anonymized user #1
Do you agree with this assessment?
D17 · Explicit Debt
6 deducted debt markers + 0 dead symbols across 8810 LoC (0.6/KLoC) → score 8.9.
EmptyCatchBlock Flyoobe/InstallView/AdvancedControlView.cs:200
What to do
- Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with ToolHelper.cs (2), AdvancedControlView.cs, BootMenuInfoProvider.cs. — One of this dimension's main actionable groups (6 issue-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Do you agree with this assessment?
D18 · Solution Shape
1 projects, 95 source files, 8810 hand-written lines of code (8810 production / 0 test), plus 3658 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 0 inter-project edges (build failed).
Monorepo: only 1 of 3 solutions was scored
Build did not complete in the analyzer
Do you agree with this assessment?
D19 · Documentation Quality
FlyOOBE's documentation is strong for a single README and an update-check HTML page but lacks depth: the main content (why FlyOOBE matters, OOBE customization features, scriptable setup extensions) appears clipped mid-sentence in the README, so the full 'Technical Overview' and 'Why Keep FlyOOBE Alive?' sections are not visible. The release download links point to a single version of FlyOOBE while the GitHub releases page is referenced (Flyby11 Classic and FlyOOBE), which would clarify what each tool does. The update-check HTML is thin but friendly; it is mostly filler over the README's content gap.
XML-doc coverage: FlyoobeFlyoobe/Flyoobe.csproj
What to do
- Improve Documentation Quality — currently 6.0/10. — FlyOOBE's documentation is strong for a single README and an update-check HTML page but lacks depth: the main content (why FlyOOBE matters, OOBE customization features, scriptable setup extensions) appears clipped mid-sentence in the README, so the full 'Technical Overview' and 'Why Keep FlyOOBE Alive?' sections are not visible. The release download links point to a single version of FlyOOBE while the GitHub releases page is referenced (Flyby11 Classic and FlyOOBE), which would clarify what each tool does. The update-check HTML is thin but friendly; it is mostly filler over the README's content gap.
Do you agree with this assessment?
D20 · ADR Quality
No architecture decision records were found.
No ADRs found
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D21 · Naming Consistency
0 naming inconsistencies across 200 sampled symbols.
Do you agree with this assessment?
D24 · Comment Value
42 valuable / 1 redundant across 200 sampled comments; 1 shown with locations.
redundant commentFlyoobe/Helper/BackgroundHelper.cs:190
Do you agree with this assessment?
D26 · Project Cohesion
0 of 1 projects flagged as possibly oversized/incoherent.
Do you agree with this assessment?
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Secret: jwtdocs/update-check.html:37
Rotate the exposed credentials — git history can't be un-committed
Do you agree with this assessment?
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
Medium: unsafe-path-combineFlyby11-deprecated/Flyby11/IsoHandler.cs:231
Do you agree with this assessment?
D34 · Knowledge Freshness
43 of 44 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Flyby11-deprecated/Flyby11/MainForm.cs.
Dormant codebase
What to do
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D35 · Change Coupling
No strong hidden change-coupling between production files.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
Do you agree with this assessment?
AX3 · Project dependency cycles
Do you agree with this assessment?
AX4 · Dependency direction
Do you agree with this assessment?
AX5 · Architecture & structure
Do you agree with this assessment?
AX6 · Interface segregation
Do you agree with this assessment?
GD1 · Unfinished & placeholder code
Do you agree with this assessment?
IC1 · Incompleteness & stubs
- `RunSelectedAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — AdvancedControlView.cs:171
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — ToolHubControlView.cs:29
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Do you agree with this assessment?
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Add a 'Testing' section to the root README — how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
Do you agree with this assessment?
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
What to do
- Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Do you agree with this assessment?
M3 · Folder & project structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
- No test surface was found — there are no tests here to separate from production code, so the folder question hasn't been reached yet.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
Do you agree with this assessment?
M4 · Documentation accuracy
Do you agree with this assessment?
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
Do you agree with this assessment?
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build.
What to do
- Run what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Do you agree with this assessment?
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Do you agree with this assessment?
X1 · Async correctness
- `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×5) — ToolHubControlView.cs:39, AiControlView.cs:20, AppsControlView.cs:341, …
What to do
- async void method: LoadTools
Do you agree with this assessment?
X2 · Cancellation propagation
- Only 0/33 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×25) — ToolHubHelper.cs:45, ToolHelper.cs:95, ToolHubControlView.cs:39, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
Do you agree with this assessment?
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — BootMenuInfoProvider.cs:74, InPlaceRepairProvider.cs:53, RunSetupFromIsoProvider.cs:52, …
What to do
- Swallowed exception (empty catch)
Do you agree with this assessment?
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 63% | Adequate | Acceptable, with room to improve. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 45% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 24% | Critical — gated by D8, D9, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 92% | Exemplary | Solid. |
Not included — 54 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — Test reliability not included
- D14 License Compliance — license scan produced no result — the tool ran but its JSON output could not be parsed; the offline NuGet fallback resolved nothing
- D22 Internal API Consistency — No exposed public API
- D23 Boundary Type-Coupling — At only 8810 LoC in a single project the codebase is trivially small despite the absence of declared bounded contexts.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read; classic .NET Framework projects are packages.config by default). No packages could be enumerated, so there was nothing to scan for NuGet CVEs — excluded rather than scored, because an unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
- D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
- D39 IL Efficiency — The target did not build, so no IL was available to measure.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this check looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
- P12 CI test-gate honesty — no CI workflow found
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — no NRT-eligible projects
- X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
- X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
Appendix A — Findings (grouped)
Issue — 8 finding(s)
D17 · Explicit Debt
- EmptyCatchBlock Flyoobe/InstallView/AdvancedControlView.cs:200
- EmptyCatchBlock Flyoobe/InstallView/BootMenuInfoProvider.cs:74
- EmptyCatchBlock Flyoobe/InstallView/InPlaceRepairProvider.cs:53
- EmptyCatchBlock Flyoobe/InstallView/RunSetupFromIsoProvider.cs:52
- EmptyCatchBlock Flyoobe/InstallView/ToolHelper.cs:55
- EmptyCatchBlock Flyoobe/InstallView/ToolHelper.cs:103
D28 · Secrets (history)
- Secret: jwt docs/update-check.html:37
D8 · Code Coverage
- No automated tests
Warning — 18 finding(s)
D1 · Cyclomatic Complexity
- ToolHubControlView.ReadMetadataFromScript (cyclomatic 22) Flyoobe/ToolHubView/ToolHubControlView.cs:124
D1 · Cyclomatic Complexity
- ToolHubItemControl.btnRun_Click (cyclomatic 21) Flyoobe/ToolHubView/ToolHubItemControl.cs:117
D1 · Cyclomatic Complexity
- BackgroundHelper.CreateBrush (cyclomatic 17) Flyoobe/Helper/BackgroundHelper.cs:188
D1 · Cyclomatic Complexity
- ToolHelpers.ResolveToolPath (cyclomatic 17) Flyoobe/InstallView/ToolHelper.cs:13
D1 · Cyclomatic Complexity
- AiControlView.DoRemove (cyclomatic 16) Flyoobe/Views/AiControlView.cs:66
D18 · Solution Shape
- Monorepo: only 1 of 3 solutions was scored
D2 · Cognitive Complexity
- ToolHelpers.ResolveToolPath (cognitive 32) Flyoobe/InstallView/ToolHelper.cs:13
D2 · Cognitive Complexity
- ToolHubControlView.ReadMetadataFromScript (cognitive 29) Flyoobe/ToolHubView/ToolHubControlView.cs:124
D2 · Cognitive Complexity
- ToolHubItemControl.btnRun_Click (cognitive 22) Flyoobe/ToolHubView/ToolHubItemControl.cs:117
D2 · Cognitive Complexity
- AiControlView.DoRemove (cognitive 20) Flyoobe/Views/AiControlView.cs:66
D2 · Cognitive Complexity
- AdvancedControlView.RunSelectedAsync (cognitive 20) Flyoobe/InstallView/AdvancedControlView.cs:171
D2 · Cognitive Complexity
- DeviceControlView.btnApply_Click (cognitive 17) Flyoobe/Views/DeviceControlView.cs:113
D2 · Cognitive Complexity
- BackgroundHelper.CreateBrush (cognitive 16) Flyoobe/Helper/BackgroundHelper.cs:188
D2 · Cognitive Complexity
- UpdatesControlView.Install (cognitive 16) Flyoobe/Views/UpdatesControlView.cs:161
D29 · Static Analysis (SAST)
- Medium: unsafe-path-combine Flyby11-deprecated/Flyby11/IsoHandler.cs:231
D4 · Code Duplication
- Duplicated block (13 lines × 16) Flyoobe/Features/Ads/FinishSetupAds.cs:33
D4 · Code Duplication
- Duplicated block (13 lines × 2) Flyoobe/Features/Edge/DefaultTopSites.cs:32
D4 · Code Duplication
- Duplicated block (10 lines × 2) Flyoobe/InstallView/InPlaceRepairProvider.cs:44
Recommendation — 7 finding(s)
D11 · Test Reliability
- Test reliability not included
D16 · Bus Factor
- Off-boarding risk: anonymized user #1
D20 · ADR Quality
- No ADRs found
D24 · Comment Value
- redundant comment Flyoobe/Helper/BackgroundHelper.cs:190
D28 · Secrets (history)
- Rotate the exposed credentials — git history can't be un-committed
D34 · Knowledge Freshness
- Dormant codebase
D9 · Test Distribution
- No tests found
Info — 3 finding(s)
D18 · Solution Shape
- Build did not complete in the analyzer
D19 · Documentation Quality
- XML-doc coverage: Flyoobe Flyoobe/Flyoobe.csproj
D22 · Internal API Consistency
- No exposed public API
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --json --quiet --timeout 0 --metrics off . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet: not applicable — `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read; classic .NET Framework projects are packages.config by default). No packages could be enumerated, so there was nothing to scan for NuGet CVEs — excluded rather than scored, because an unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess. | 0 | — |
| D33 · JS/npm Dependency Vulnerabilities | trivy | — | trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D38 · OSV Dependency Vulnerabilities | osv-scanner | — | osv-scanner: not applicable — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |