Public report — Revival Of Forests, published 18 Jun 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
Medium · 51,270 LoC · 5 projects · rebuild ~1.2 person-years · weakest lens: Maturity (31%)
Build did not compile — scores are provisional
The analysed solution did not compile (35 build error(s)). Dimensions that depend on the compiler — complexity, duplication, cohesion, dead code, API surface — ran on incomplete models, so the scores below are provisional. Fix the build, then re-run for a reliable grade. First errors: CS0117: 'UnitDefinitionData' does not contain a definition for 'UnitType'; CS1503: Argument 2: cannot convert from 'string' to 'Canine.TacticalBattleEngine.Core.UnitType'; CS0029: Cannot implicitly convert type 'Canine.TacticalBattleEngine.Core.UnitType' to 'string'
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
418findings with an exact file:lineof 449 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
43/92dimensions across the health lenses51270 LoC · 5 projects — wide & deep
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.
Revival Of Forests carries serious gaps (47%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
The area that most needs attention is Maturity (31%) — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent. Readiness (58%) is the next concern — 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.
Leadership focus, highest impact first: 50 Secret finding(s) (Secrets (history)); 1 No ADRs found finding(s) in ADR Quality (ADR Quality); Make the call chain async end-to-end and await it (Async & latency hygiene).
For scale: Medium (~51,270 production lines); rebuilding it from scratch would take roughly ~1.2 person-years (~1–3 engineers). Approximate, ±~30%.
This codebase represents roughly ~1.2 person-years of build effort (about ~€170,000 to rebuild). Its weakest lens is Maturity at 31% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — library/CLI, high decision density × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Highest-leverage move: fix the build · Critical · Leverage
The solution doesn't compile, so every Roslyn-derived dimension (complexity, duplication, cohesion, dead code, API surface) ran on incomplete models and is PROVISIONAL. Fixing the build is the single change that makes the rest of the report trustworthy — do it first. The compiler reported: CS0117: 'UnitDefinitionData' does not contain a definition for 'UnitType'; CS1503: Argument 2: cannot convert from 'string' to 'Canine.TacticalBattleEngine.Core.UnitType'; CS0029: Cannot implicitly convert type 'Canine.TacticalBattleEngine.Core.UnitType' to 'string'.
Evidence: D18 build: The compiler reported: CS0117: 'UnitDefinitionData' does not contain a definition for 'UnitType'; CS1503: Argument 2: cannot convert from 'string' to 'Canine.TacticalBattleEngine.Core.UnitType'; CS0029: Cannot implicitly convert type 'Canine.TacticalBattleEngine.Core.UnitType' to 'string'.
→ Fix the build, then re-run for a reliable grade.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~1.2 person-years to rebuild), and its weakest lens is Maturity at 31%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Maturity first — highest risk-reduction per euro on an asset this size.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
At a glance — Code Health · 61% · Fair · gated by D18, X1
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A02:2021 — Cryptographic Failures
51
High / Critical
A06:2021 — Vulnerable & Outdated Components
2
High / Critical
Roadmap
Top priorities: Resolve the 50 Secret finding(s) in Secrets (history) — start with Corporation building.tscn (13), Stone large 2.tscn (4), Stone small 3.tscn (4); Resolve the 1 No ADRs found finding(s) in ADR Quality; Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.
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. 43 of 43 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.6 — 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.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 43 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
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, 418 of 449 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
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.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — LLM provider failed — The model provider was unreachable or errored, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
D21 Naming Consistency — LLM provider failed — The model provider was unreachable or errored, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
D23 Boundary Type-Coupling — evaluation did not complete — Dimension evaluation failed — excluded from the score.
D24 Comment Value — LLM provider failed — The model provider was unreachable or errored, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
D26 Project Cohesion — evaluation did not complete — Dimension evaluation failed — excluded from the score.
D31 IaC & Container Security — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D32 Data Compliance (PII/GDPR) — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D33 JS/npm Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D36 Supply-chain Provenance & Signing — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D37 Vulnerability-disclosure Policy — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D38 OSV Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
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
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
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 (EF migration scaffolds, *.Designer.cs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only; the generated footprint is reported separately under Solution Shape.
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.
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
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.
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 (EF migrations, designer files, snapshots) 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.
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.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
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").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
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 ADVISORY: an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being unhealthy.
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.
The LLM boundary
LLM-set scores this run (3): D20, D22, M4 (model: openai-compatible). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 31 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 UnitAI.MakeOperationalDecision (cyclomatic 51) finding(s) in Cyclomatic Complexity — start with UnitAI.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 WaypointMovementSystem.ProcessMovementTick (cyclomatic 40) finding(s) in Cyclomatic Complexity — start with WaypointMovementSystem.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 AnimationLookupSystem.FuzzyMatchAnimationType (cyclomatic 35) finding(s) in Cyclomatic Complexity — start with AnimationLookupSystem.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 71 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 UnitAI.MakeOperationalDecision (cognitive 111) finding(s) in Cognitive Complexity — start with UnitAI.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CombatSystem.ProcessCombatTick (cognitive 86) finding(s) in Cognitive Complexity — start with CombatSystem.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 WaypointMovementSystem.ProcessMovementTick (cognitive 78) finding(s) in Cognitive Complexity — start with WaypointMovementSystem.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.1 / 10Exemplary✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
+ 15 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 10 Low cohesion finding(s) in Cohesion (LCOM4) — start with BasicCardSystem.cs, BattlefieldManager.cs, GoldManaResourceSystem.cs. — One of this dimension's main actionable groups (10 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
1966 test methods: 1966 unit, 0 integration, 0 BDD, 0 e2e.
Unit tests
Integration tests
BDD tests
E2E tests
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
6 skipped (6 with a documented reason), 6 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1966 tests.
No assertions: ReproduceBDDAmmunitionBug_WeaponSystemFiresButNoEventsSet · ×6Canine/Canine.TacticalBattleEngine.Tests/DebugTests/BDDAmmunitionBugTest.cs:17
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
Dead code: UpdateTeamColor · ×14RevivalOfForest/ROF.Game/Scripts/Combat/ProjectileRenderer.cs:285
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape3.0 / 10Poor✓ Tool-verified
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API Consistency / 10Exemplary◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
80 % of calls cross a namespace and 0 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
3354 finding(s): 0 critical, 3354 high, 0 medium, 0 low. Remediation is credential rotation — the secrets remain in history regardless of later deletion.
Secret: aws-access-token · ×50RevivalOfForest/ROF.Game/Assets/Buildings/Civilian houses/Concrete fencing 3.tscn:23detected by gitleaks finding
Rotate the exposed credentials — git history can't be un-committed
What to do
Resolve the 50 Secret finding(s) in Secrets (history) — start with Corporation building.tscn (13), Stone large 2.tscn (4), Stone small 3.tscn (4). — One of this dimension's main actionable groups (50 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep --config auto across the repo; severity rules (ERROR/WARNING/INFO) map to a 0-10 wide normalizer. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
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).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
~51.3k production LoC (740 types) across 3 project(s) / 53 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
What to do
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
A test is skipped ("ProcessCombatCacheFriendly method was removed during refactoring. This behavior is covered by Step2 (CombatSystem level) and Step5 (full simulation level).") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — IsolateRangeBugStepByStepTest.cs:112
A test is skipped ("Obsolete: Wave-based spawning doesn't create default units for empty composition rules") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — SpawnAreaUnitFactoryTests.cs:15, SpawnAreaUnitFactoryTests.cs:21
A test is skipped ("Obsolete: CreateDefaultUnit method removed in wave-based spawning refactoring") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×3) — SpawnAreaUnitFactoryTests.cs:129, SpawnAreaUnitFactoryTests.cs:135, SpawnAreaUnitFactoryTests.cs:141
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×9) — PineBranch.cs:10, PineBranch.cs:11, UnitSelectButton.cs:211, …
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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
No README at the repository root — newcomers have no entry point.
What to do
Add a root README: what the system is, how to build/run it, and a map of the projects.
Add a README to the 2 of 5 project(s) that lack one — worth up to 0.8 pts.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
There is no README, so nothing documents what the system is or how it works.
What to do
Add a README describing the system, how to build/run it, and keep it current.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
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.
Readiness · Readiness — Whether behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.
Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem/Roslyn scan: CodeQL, Dependabot, secret-scanning, and BenchmarkDotNet presence in pipelines and projects. Exhaustive, deterministic.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Performance — Whether the library protects its performance with benchmarks — a BenchmarkDotNet suite, an allocation MemoryDiagnoser, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's GC — Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask, value-type structs and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Raise allocation-aware density on the hot paths — currently 24 use(s) across 51,341 production line(s) (~0.5/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code keeps its host responsive — a library awaits with ConfigureAwait(false) (so it never captures and stalls the host's context) and avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a library with ≥5 awaits — the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock in a consumer with a synchronization context.
Only 0/76 awaits use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code.
In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
Do you agree with this assessment?
X1 · Async correctness3.7 / 10Poor✓ Tool-verified
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` unless this is a top-level event handler. (×21) — GrassFieldManager.cs:118, TransitionManager.cs:250, TransitionManager.cs:386, …
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Make the caller `async` and `await` instead. — TacticalSimulator.cs:261
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage.
Only 0/48 async methods accept a CancellationToken, so requests can't be cancelled cleanly under load or on client disconnect. In Blazor Server circuits and other short-write hosts, omitting it can be an accepted convention — judge against your hosting model.
No CancellationToken parameter — work can't be cancelled cleanly on disconnect/shutdown. (×25) — GrassDataCache.cs:53, GrassFieldManager.cs:118, GrassFieldManager.cs:126, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
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. — TreeSortingHelper.cs:190
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.0 `!` suppressions per 1k syntax nodes — each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Not included — 49 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
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
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.
D11 Test Reliability — No tests discovered
D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
D33 JS/npm Dependency Vulnerabilities — Not applicable
D34 Knowledge Freshness — early-stage repository — too little history to judge knowledge freshness
D35 Change Coupling — no production change history to mine for change-coupling
D36 Supply-chain Provenance & Signing — Not applicable
D37 Vulnerability-disclosure Policy — Not applicable
D38 OSV Dependency Vulnerabilities — Not applicable
D7 Architectural Integrity — No checkable ADRs to assess
D8 Code Coverage — Coverage not measured
DM1 Domain Modelling — not run — only 2/3 markers (9 strongly-typed id(s); 11 value object(s))
ED1 Event-Driven — not run — 0/3 markers found
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not run — 0/3 markers found
P12 CI test-gate honesty — no CI workflow found
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
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
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
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 — run tests with `--collect:"XPlat Code Coverage"` (or in CI) to enable this cross-layer check
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.
X6 Hand-rolled structured-format parsing — no data
X7 Silent fallback defaults — no data
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
No assertions: ReproduceBDDAmmunitionBug_WeaponSystemFiresButNoEventsSet Canine/Canine.TacticalBattleEngine.Tests/DebugTests/BDDAmmunitionBugTest.cs:17— Test method has no assertions — it may not test anything.
No assertions: Forest_Movement_Speed_Calculation Canine/Canine.TacticalBattleEngine.Tests/UnitTests/ForestMovesToPOITest.cs:92— Test method has no assertions — it may not test anything.
No assertions: PathfindingSystem_ShouldShowCoordinateMapping Canine/Canine.TacticalBattleEngine.Tests/UnitTests/PathfindingDebuggingTests.cs:90— Test method has no assertions — it may not test anything.
No assertions: SetWalkable_ShouldHandleInvalidPositions Canine/Canine.TacticalBattleEngine.Tests/UnitTests/PathfindingGridTests.cs:180— Test method has no assertions — it may not test anything.
No assertions: AddStaticObstacle_ShouldHandleEdgeCases Canine/Canine.TacticalBattleEngine.Tests/UnitTests/PathfindingGridTests.cs:211— Test method has no assertions — it may not test anything.
No assertions: Check_What_MockWeapon_Properties_Are_Used Canine/Canine.TacticalBattleEngine.Tests/UnitTests/TargetSelectionRangeBugTest.cs:122— Test method has no assertions — it may not test anything.
High CVE: System.Net.Http 4.3.0 — System.Net.Http 4.3.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Text.RegularExpressions 4.3.0 — System.Text.RegularExpressions 4.3.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
TodoComment RevivalOfForest/ROF.Game/Assets/UI/UnitSelectButton.cs:210— // TODO: Economy integration - show cost from unit.PurchaseCost — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Assets/UI/UnitSelectButton.cs:452— // TODO: Economy system integration — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Assets/UI/UnitSelectButton.cs:466— // TODO: Show purchase confirmation dialog — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Assets/UI/UnitSelectButton.cs:467— // TODO: Play purchase sound effect — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Assets/UI/UnitSelectButton.cs:468— // TODO: Update player currency display — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Assets/UI/UnitSelectButton.cs:472— // TODO: Show insufficient funds dialog — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Assets/UI/UnitSelectButton.cs:695— // TODO: This should be moved to GameLogic layer with deterministic generation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Assets/UI/UnitSelectButton.cs:748— // TODO: Play unit placement sound — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Assets/UI/UnitSelectButton.cs:749— // TODO: Show placement confirmation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/Animation/AnimationCache.cs:95— // TODO: Get from unit definition when multiple skeletons supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/Environment/NeutralUnitRenderer.cs:14— // TODO: Load from GameSettings Resource when Resource loading system is implemented — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/Managers/BattlefieldManager.cs:2144— // TODO: Store target priority on UnitLogicRenderer if needed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/Resources/ResourceManager.cs:190— // TODO: Load DeathEffect if needed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/MainMenuScene.cs:282— // TODO: Implement save game functionality — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/MainMenuScene.cs:301— // TODO: Implement credits screen — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/ExperienceEditDialog.cs:133— // TODO: Add Name field to ExperienceConfiguration — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/ExperienceEditDialog.cs:149— // TODO: Add Name field to StatBonusConfiguration — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/ExperienceEditDialog.cs:151— // TODO: Determine which bonus type is being edited — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/ExperienceEditDialog.cs:153— // TODO: This should be per-level bonus — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/ExperienceEditDialog.cs:155— // TODO: StatBonusConfiguration doesn't have a BonusType field - it has different bonus types as separate fields — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/ExperienceEditDialog.cs:240— // TODO: Create new ExperienceConfiguration with updated values — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/ExperienceEditDialog.cs:248— // TODO: Create new StatBonusConfiguration with updated values — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/GameSettingsOverview.cs:64— // TODO: Implement game settings loading when ResourceManager supports it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/GameSettingsOverview.cs:77— // TODO: Implement settings panel population based on GameSettings structure — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/GameSettingsOverview.cs:96— // TODO: Create controls for simulation settings — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
Dead code: UpdateTeamColor RevivalOfForest/ROF.Game/Scripts/Combat/ProjectileRenderer.cs:285— Method UpdateTeamColor — no references found in solution.
Dead code: DrawMovementPreview RevivalOfForest/ROF.Game/Scripts/Managers/BattlefieldManager.cs:988— Method DrawMovementPreview — no references found in solution.
Dead code: RegisterTreeAsNeutralUnit RevivalOfForest/ROF.Game/Scripts/Managers/ProceduralForestManager.cs:236— Method RegisterTreeAsNeutralUnit — no references found in solution.
Dead code: PopulateTree RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/DefenceOverview.cs:157— Method PopulateTree — no references found in solution.
Dead code: PopulateTree RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/UnitsOverview.cs:169— Method PopulateTree — no references found in solution.
Dead code: PopulateTree RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/WeaponsOverview.cs:136— Method PopulateTree — no references found in solution.
Dead code: ConvertUnitStatesToUnitStates Canine/Canine.TacticalBattleEngine.Tests/BehaviorTests/UnitMovementBehaviorTests.cs:157— Method ConvertUnitStatesToUnitStates — no references found in solution.
Dead code: UpdateUnitStatesFromUnitStates Canine/Canine.TacticalBattleEngine.Tests/BehaviorTests/UnitMovementBehaviorTests.cs:188— Method UpdateUnitStatesFromUnitStates — no references found in solution.
Dead code: CreateComplexScenario Canine/Canine.TacticalBattleEngine.Tests/Integration/EndToEndSimulationTests.cs:268— Method CreateComplexScenario — no references found in solution.
Dead code: CreateComplexCommands Canine/Canine.TacticalBattleEngine.Tests/Integration/EndToEndSimulationTests.cs:313— Method CreateComplexCommands — no references found in solution.
Dead code: InvokePrivateMethod Canine/Canine.TacticalBattleEngine.Tests/UnitTests/RotationSystemTests.cs:371— Method InvokePrivateMethod — no references found in solution.
Dead code: ApplySplashDamageToUnit Canine/Canine.TacticalBattleEngine/Combat/SplashDamageSystem.cs:60— Method ApplySplashDamageToUnit — no references found in solution.
Dead code: DetermineHitResult Canine/Canine.TacticalBattleEngine/Combat/WeaponSystem.cs:218— Method DetermineHitResult — no references found in solution.
Dead code: CalculateTangentialAvoidance Canine/Canine.TacticalBattleEngine/Navigation/CollisionAvoidanceSystem.cs:332— Method CalculateTangentialAvoidance — no references found in solution.
Low cohesion: ResourceManager (LCOM4 8) RevivalOfForest/ROF.Game/Scripts/Resources/ResourceManager.cs:23— ResourceManager's methods form 8 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: UnitEditDialog (LCOM4 6) RevivalOfForest/ROF.Game/Scripts/UI/ModdingTools/UnitEditDialog/UnitEditDialog.cs:20— UnitEditDialog's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: UnitLogicRenderer (LCOM4 5) RevivalOfForest/ROF.Game/Scripts/UnitLogicRenderer.cs:15— UnitLogicRenderer's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: BasicCardSystem (LCOM4 5) Canine/Canine.TacticalBattleEngine/Modules/Cards/BasicCardSystem.cs:8— BasicCardSystem's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TowerfallConfiguration (LCOM4 5) TowerfallProtocol/Towerfall.Game/Scripts/Configuration/TowerfallConfiguration.cs:15— TowerfallConfiguration's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: BattlefieldManager (LCOM4 4) RevivalOfForest/ROF.Game/Scripts/Managers/BattlefieldManager.cs:20— BattlefieldManager's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TeamBasedFactions (LCOM4 4) Canine/Canine.TacticalBattleEngine/Modules/Factions/TeamBasedFactions.cs:10— TeamBasedFactions's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: GoldManaResourceSystem (LCOM4 4) Canine/Canine.TacticalBattleEngine/Modules/Resources/GoldManaResourceSystem.cs:8— GoldManaResourceSystem's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: SimulationRngProvider (LCOM4 4) Canine/Canine.TacticalBattleEngine/Simulation/SimulationRngProvider.cs:7— SimulationRngProvider's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: SinglePlayerLogic (LCOM4 4) Canine/Canine.TacticalBattleEngine/Simulation/SinglePlayerLogic.cs:9— SinglePlayerLogic's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
XxxComment RevivalOfForest/ROF.Game/Scripts/Animation/AnimationFileLoader.cs:135— // Weapon format: WPN-XXX (contains hyphen, e.g., WPN-003, WPN-009) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment RevivalOfForest/ROF.Game/Scripts/Animation/AnimationFileLoader.cs:147— // Unit format: MON-XXX or UNIT-XXX (contains hyphen) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment RevivalOfForest/ROF.Game/Scripts/Animation/AnimationLookupSystem.cs:82— // Look for pattern "WPN XXX" at the start — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment RevivalOfForest/ROF.Game/Scripts/Animation/AnimationLookupSystem.cs:150— // Look for pattern ANM-XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment RevivalOfForest/ROF.Game/Scripts/Managers/UnitRegistry.cs:18— // Maps HRO XXX to definitions — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment RevivalOfForest/ROF.Game/Scripts/Managers/UnitRegistry.cs:19— // Maps MST XXX to definitions — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment Canine/Canine.TacticalBattleEngine/Animation/AnimationFilenameParser.cs:238— // This marks the end of the ID section (SKL-XXX, WPN-XXX, UNIT-XXX, MON-XXX) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
Build failed — The target solution did not build cleanly (errors: 35), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0117: 'UnitDefinitionData' does not contain a definition for 'UnitType'; CS1503: Argument 2: cannot convert from 'string' to 'Canine.TacticalBattleEngine.Core.UnitType'; CS0029: Cannot implicitly convert type 'Canine.TacticalBattleEngine.Core.UnitType' to 'string'.
Monorepo: only 1 of 2 solutions was scored — This repository contains 2 .NET solutions, but a scan analyzes ONE. Every score, lens, and finding here reflects only `CanineStudio.sln` — the other 1 (`ROF.sln`) were not analyzed and are not represented in the headline. To cover them, scan each solution as its own target and group them in a Solution or Product for a portfolio roll-up. If a secondary solution is an archived or vendored tree, declare it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — to exclude it from discovery the same way generated code is.
Off the main sequence: Canine.TacticalBattleEngine — Canine.TacticalBattleEngine: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Coverage not measured — The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. Commit the Cobertura/OpenCover/lcov report your CI already produces (anywhere in the repo), or make the suite runnable in-image, and real coverage will be measured.
no ADRs to check — No ADRs found, so conformance can't be assessed.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Rotate the exposed credentials — git history can't be un-committed — These secrets are in git HISTORY: deleting the file does not remove them (the commit persists on every clone, fork and backup). The remediation is to ROTATE each exposed credential and treat it as compromised — not to delete the file. Rewriting history is disruptive and unreliable across existing forks.
D31 · IaC & Container Security· Not applicable · ×1
Not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 · Data Compliance (PII/GDPR)· Not applicable · ×1
Not applicable — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D33 · JS/npm Dependency Vulnerabilities· Not applicable · ×1
Not applicable — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
early-stage repository — too little history to judge knowledge freshness — early-stage repository — too little history to judge knowledge freshness (0 commit(s) sampled).
D36 · Supply-chain Provenance & Signing· Not applicable · ×1
Not applicable — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
D37 · Vulnerability-disclosure Policy· Not applicable · ×1
Not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D38 · OSV Dependency Vulnerabilities· Not applicable · ×1
Not applicable — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
D7 · Architectural Integrity· No checkable ADRs to assess · ×1
No checkable ADRs to assess — No architecture decision records were found and the project graph is acyclic, so architectural integrity could not be assessed. Add ADRs (with `enforcement: analyzer|test`) to make the architecture's rules checkable.
Justified suppression RevivalOfForest/ROF.Game/Scripts/Environment/GrassFieldManager.cs:233— #pragma warning disable CA2000 // Dispose objects before losing scope - QuadMesh is shared and managed by Godot
Justified suppression RevivalOfForest/ROF.Game/Scripts/Environment/GrassFieldManager.cs:292— #pragma warning disable CA2000 // Dispose objects before losing scope - Node is added to scene tree and managed by Godot
Skipped (documented): Step3_ProcessCombatCacheFriendly_Should_Find_No_Engagements Canine/Canine.TacticalBattleEngine.Tests/UnitTests/IsolateRangeBugStepByStepTest.cs:112— Skipped with a documented reason — a deferral, not lazy debt: ProcessCombatCacheFriendly method was removed during refactoring. This behavior is covered by Step2 (CombatSystem level) and Step5 (full simulation level).
Skipped (documented): SpawnUnits_WithNoCompositionRules_CreatesDefaultUnit Canine/Canine.TacticalBattleEngine.Tests/UnitTests/SpawnAreaUnitFactoryTests.cs:15— Skipped with a documented reason — a deferral, not lazy debt: Obsolete: Wave-based spawning doesn't create default units for empty composition rules
Skipped (documented): SpawnUnits_WithEmptyCompositionRules_CreatesDefaultUnit Canine/Canine.TacticalBattleEngine.Tests/UnitTests/SpawnAreaUnitFactoryTests.cs:21— Skipped with a documented reason — a deferral, not lazy debt: Obsolete: Wave-based spawning doesn't create default units for empty composition rules
Skipped (documented): CreateDefaultUnit_GeneratesUnitWithCorrectProperties Canine/Canine.TacticalBattleEngine.Tests/UnitTests/SpawnAreaUnitFactoryTests.cs:129— Skipped with a documented reason — a deferral, not lazy debt: Obsolete: CreateDefaultUnit method removed in wave-based spawning refactoring
Skipped (documented): CreateDefaultUnit_IsDeterministic Canine/Canine.TacticalBattleEngine.Tests/UnitTests/SpawnAreaUnitFactoryTests.cs:135— Skipped with a documented reason — a deferral, not lazy debt: Obsolete: CreateDefaultUnit method removed in wave-based spawning refactoring
Skipped (documented): CreateDefaultUnit_WithDifferentTeams_UsesCorrectTeam Canine/Canine.TacticalBattleEngine.Tests/UnitTests/SpawnAreaUnitFactoryTests.cs:141— Skipped with a documented reason — a deferral, not lazy debt: Obsolete: CreateDefaultUnit method removed in wave-based spawning refactoring
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
trivy: not applicable — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
provenance: not applicable — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
osv-scanner: not applicable — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
0
—
Run 019edc7e-0894-7610-b527-12e8dbdad1aa · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 1 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by name with a deliberately specific classifier (the same one the GDPR dimensions use, so CardDefinition or FileName don't trip); informational — it feeds no score.
Issues: 63 · Warnings: 268 · Recommendations: 13 · Info: 105 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 18-06-2026 @ 20:48 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.