Executive summary
k1tbyte/Wand-Enhancer has a provisional result, because the code didn't build. Its score is held back because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 45 out of 100, and the ratings may change once the code builds. 13 of its 23 critical findings are security problems.
Production Readiness, at 35, is the weakest lens and counts most in the score. The best first step is handling the discarded errors, worth about 5 points. Adding a diagnostic log would lift Production Readiness itself, also worth about 5. Raising Production Readiness to 70 would lift the score to about 54.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three known security holes in the packages the code depends on can be used by attackers, and eight errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, updating the vulnerable packages and handling or logging the ignored errors would close these risks. Fixing the weaknesses the scanner points to would fix the three security weaknesses in the code, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 6,478 lines, about €13,000 to rebuild.
If Production Readiness rose from 35 to 70, the lowest score rated Strong, the score would rise from 45 to about 54.
New since the last survey: 14 findings
- Code Duplication · Edited copy of a member (11 corresponding lines) WandEnhancer/Utils/WeModInstalls.cs
- Code Duplication · Edited copy of a member (28 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (11 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (6 corresponding lines) AsarSharp/PickleTools/Pickle.cs
- Churn × Complexity Hotspots · Repeated repair: REDACTED REDACTED
- Explicit Debt · EmptyCatchBlock WandEnhancer/View/MainWindow/MainWindowVm.cs
- Dependency Vulnerabilities · REDACTED
- Async correctness · async void method: OnDrop WandEnhancer/View/MainWindow/MainWindow.xaml.cs
- Async correctness · async void method: OnFolderPathSelection WandEnhancer/View/MainWindow/MainWindowVm.cs
- Async correctness · async void method: OnRescanInstall WandEnhancer/View/MainWindow/MainWindowVm.cs
- Cancellation propagation · Async method without CancellationToken: PickInstallAsync WandEnhancer/View/MainWindow/MainWindowVm.cs
- Exception handling · Swallowed exception (empty catch) WandEnhancer/View/MainWindow/MainWindowVm.cs
- Stateful singletons · Process-global static state: LauncherLog WandEnhancer/Core/LauncherLog.cs
- Stateful singletons · Process-global static state: LocalizationManager WandEnhancer/Core/Services/LocalizationManager.cs
Fixed since the last survey: 5 findings
- Static Analysis (SAST) · High: REDACTED .github/workflows/build.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/build.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/build.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/build.yml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,300 to €22,000, for 72 to 236 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,478 lines of product code |
| Comment lines | The estimate prices 6,060 lines. Comment lines count towards the size of 6,478 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 AsarSharp.Integrity | 2 AsarSharp.PickleTools | 3 AsarSharp.Utils | 4 WandEnhancer.Converters | 5 WandEnhancer.Core.Js | 6 WandEnhancer.Models | 7 WandEnhancer.ReactiveUICore | 8 WandEnhancer.View.Controls | 9 scripts.diagnostics | 10 web-panel.bridge | 11 web-panel.bridge.scripts.default | 12 web-panel.bridge.scripts.default.installed-apps-sync | 13 web-panel.bridge.scripts.default.remote-popup-cleanup | 14 web-panel.bridge.src.types | 15 web-panel.bridge.src.wand | 16 web-panel.protocol | 17 web-panel.protocol.messages | 18 web-panel.src.remote-session.remote-session_reducer | 19 AsarSharp.AsarFileSystem | 20 WandEnhancer.Core.Patching.Strategies | 21 WandEnhancer.Utils | 22 WandEnhancer.View.Popups | 23 web-panel.bridge.src | 24 web-panel.bridge.src.normalizers | 25 web-panel.src.library.model | 26 web-panel.src.remote-session | 27 web-panel.src.remote-session.remote-session_client | 28 web-panel.src.trainer.controls | 29 web-panel.src.trainer.model | 30 web-panel.src.trainer.pinned-cheats | 31 web-panel.src.trainer.ui | 32 AsarSharp | 33 WandEnhancer.Core | 34 WandEnhancer | 35 WandEnhancer.Core.Patching.Content | 36 WandEnhancer.Core.Patching.Shared | 37 WandEnhancer.Core.Patching.Strategies.Static | 38 WandEnhancer.Core.Patching.Strategies.Supervised | 39 WandEnhancer.Core.Services | 40 WandEnhancer.View.MainWindow |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 AsarSharp.Integrity | ||||||||||||||||||||||||||||||||||||||||
| 2 AsarSharp.PickleTools | ||||||||||||||||||||||||||||||||||||||||
| 3 AsarSharp.Utils | ||||||||||||||||||||||||||||||||||||||||
| 4 WandEnhancer.Converters | ||||||||||||||||||||||||||||||||||||||||
| 5 WandEnhancer.Core.Js | ||||||||||||||||||||||||||||||||||||||||
| 6 WandEnhancer.Models | ||||||||||||||||||||||||||||||||||||||||
| 7 WandEnhancer.ReactiveUICore | ||||||||||||||||||||||||||||||||||||||||
| 8 WandEnhancer.View.Controls | ||||||||||||||||||||||||||||||||||||||||
| 9 scripts.diagnostics | ||||||||||||||||||||||||||||||||||||||||
| 10 web-panel.bridge | ||||||||||||||||||||||||||||||||||||||||
| 11 web-panel.bridge.scripts.default | ||||||||||||||||||||||||||||||||||||||||
| 12 web-panel.bridge.scripts.default.installed-apps-sync | ||||||||||||||||||||||||||||||||||||||||
| 13 web-panel.bridge.scripts.default.remote-popup-cleanup | ||||||||||||||||||||||||||||||||||||||||
| 14 web-panel.bridge.src.types | ||||||||||||||||||||||||||||||||||||||||
| 15 web-panel.bridge.src.wand | ||||||||||||||||||||||||||||||||||||||||
| 16 web-panel.protocol | ||||||||||||||||||||||||||||||||||||||||
| 17 web-panel.protocol.messages | ||||||||||||||||||||||||||||||||||||||||
| 18 web-panel.src.remote-session.remote-session_reducer | ||||||||||||||||||||||||||||||||||||||||
| 19 AsarSharp.AsarFileSystem | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 WandEnhancer.Core.Patching.Strategies | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 WandEnhancer.Utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 WandEnhancer.View.Popups | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 web-panel.bridge.src | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 24 web-panel.bridge.src.normalizers | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 web-panel.src.library.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 web-panel.src.remote-session | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 web-panel.src.remote-session.remote-session_client | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 web-panel.src.trainer.controls | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 web-panel.src.trainer.model | 5 | |||||||||||||||||||||||||||||||||||||||
| 30 web-panel.src.trainer.pinned-cheats | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 web-panel.src.trainer.ui | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 AsarSharp | 4 | |||||||||||||||||||||||||||||||||||||||
| 33 WandEnhancer.Core | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 WandEnhancer | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 WandEnhancer.Core.Patching.Content | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 36 WandEnhancer.Core.Patching.Shared | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 WandEnhancer.Core.Patching.Strategies.Static | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 WandEnhancer.Core.Patching.Strategies.Supervised | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 WandEnhancer.Core.Services | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 WandEnhancer.View.MainWindow | 1 | 2 | 2 |
19→1 AsarSharp.AsarFileSystem uses AsarSharp.Integrity✕
- Connections
- 2 pairs of types, where a type in AsarSharp.AsarFileSystem uses a type in AsarSharp.Integrity.
- The types involved
AsarSharp.AsarFileSystem.Filesystem→AsarSharp.Integrity.FileIntegrityAsarSharp.AsarFileSystem.FilesystemEntry→AsarSharp.Integrity.FileIntegrity
- Direction
- AsarSharp.AsarFileSystem uses AsarSharp.Integrity, so a change to AsarSharp.Integrity can break AsarSharp.AsarFileSystem, while a change to AsarSharp.AsarFileSystem can't break AsarSharp.Integrity.
- Position
- Below the diagonal: AsarSharp.AsarFileSystem uses a module listed above it, which is the healthy direction.
19→2 AsarSharp.AsarFileSystem uses AsarSharp.PickleTools✕
- Connections
- 1 pair of types, where a type in AsarSharp.AsarFileSystem uses a type in AsarSharp.PickleTools.
- The types involved
AsarSharp.AsarFileSystem.Disk→AsarSharp.PickleTools.Pickle
- Direction
- AsarSharp.AsarFileSystem uses AsarSharp.PickleTools, so a change to AsarSharp.PickleTools can break AsarSharp.AsarFileSystem, while a change to AsarSharp.AsarFileSystem can't break AsarSharp.PickleTools.
- Position
- Below the diagonal: AsarSharp.AsarFileSystem uses a module listed above it, which is the healthy direction.
20→6 WandEnhancer.Core.Patching.Strategies uses WandEnhancer.Models✕
- Connections
- 2 pairs of types, where a type in WandEnhancer.Core.Patching.Strategies uses a type in WandEnhancer.Models.
- The types involved
WandEnhancer.Core.Patching.Strategies.PatchContext→WandEnhancer.Models.WeModConfigWandEnhancer.Core.Patching.Strategies.StrategyFactory→WandEnhancer.Models.EPatchStrategy
- Direction
- WandEnhancer.Core.Patching.Strategies uses WandEnhancer.Models, so a change to WandEnhancer.Models can break WandEnhancer.Core.Patching.Strategies, while a change to WandEnhancer.Core.Patching.Strategies can't break WandEnhancer.Models.
- Position
- Below the diagonal: WandEnhancer.Core.Patching.Strategies uses a module listed above it, which is the healthy direction.
20→33 WandEnhancer.Core.Patching.Strategies uses WandEnhancer.Core part of a loop✕
- Connections
- 1 pair of types, where a type in WandEnhancer.Core.Patching.Strategies uses a type in WandEnhancer.Core.
- The types involved
WandEnhancer.Core.Patching.Strategies.PatchContext→WandEnhancer.Core.ELogType
- Direction
- WandEnhancer.Core.Patching.Strategies uses WandEnhancer.Core, so a change to WandEnhancer.Core can break WandEnhancer.Core.Patching.Strategies, while a change to WandEnhancer.Core.Patching.Strategies can't break WandEnhancer.Core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→6 WandEnhancer.Utils uses WandEnhancer.Models✕
- Connections
- 1 pair of types, where a type in WandEnhancer.Utils uses a type in WandEnhancer.Models.
- The types involved
WandEnhancer.Utils.WeModInstalls→WandEnhancer.Models.WeModConfig
- Direction
- WandEnhancer.Utils uses WandEnhancer.Models, so a change to WandEnhancer.Models can break WandEnhancer.Utils, while a change to WandEnhancer.Utils can't break WandEnhancer.Models.
- Position
- Below the diagonal: WandEnhancer.Utils uses a module listed above it, which is the healthy direction.
22→6 WandEnhancer.View.Popups uses WandEnhancer.Models✕
- Connections
- 2 pairs of types, where a type in WandEnhancer.View.Popups uses a type in WandEnhancer.Models.
- The types involved
WandEnhancer.View.Popups.PatchVectorsPopup→WandEnhancer.Models.PatchConfigWandEnhancer.View.Popups.StrategyItem→WandEnhancer.Models.EPatchStrategy
- Direction
- WandEnhancer.View.Popups uses WandEnhancer.Models, so a change to WandEnhancer.Models can break WandEnhancer.View.Popups, while a change to WandEnhancer.View.Popups can't break WandEnhancer.Models.
- Position
- Below the diagonal: WandEnhancer.View.Popups uses a module listed above it, which is the healthy direction.
23→14 web-panel.bridge.src uses web-panel.bridge.src.types✕
- Connections
- 2 pairs of types, where a type in web-panel.bridge.src uses a type in web-panel.bridge.src.types.
- The types involved
web-panel.bridge.src.logger→web-panel.bridge.src.types.BridgeLoggerweb-panel.bridge.src.logger→web-panel.bridge.src.types.LogLevel
- Direction
- web-panel.bridge.src uses web-panel.bridge.src.types, so a change to web-panel.bridge.src.types can break web-panel.bridge.src, while a change to web-panel.bridge.src can't break web-panel.bridge.src.types.
- Position
- Below the diagonal: web-panel.bridge.src uses a module listed above it, which is the healthy direction.
23→17 web-panel.bridge.src uses web-panel.protocol.messages✕
- Connections
- 4 pairs of types, where a type in web-panel.bridge.src uses a type in web-panel.protocol.messages.
- The types involved
web-panel.bridge.src.index→web-panel.protocol.messages.CheatArgsweb-panel.bridge.src.index→web-panel.protocol.messages.InstalledAppSummaryweb-panel.bridge.src.index→web-panel.protocol.messages.InstalledAppsPayloadweb-panel.bridge.src.server→web-panel.protocol.messages.IncomingMessage
- Direction
- web-panel.bridge.src uses web-panel.protocol.messages, so a change to web-panel.protocol.messages can break web-panel.bridge.src, while a change to web-panel.bridge.src can't break web-panel.protocol.messages.
- Position
- Below the diagonal: web-panel.bridge.src uses a module listed above it, which is the healthy direction.
24→17 web-panel.bridge.src.normalizers uses web-panel.protocol.messages✕
- Connections
- 1 pair of types, where a type in web-panel.bridge.src.normalizers uses a type in web-panel.protocol.messages.
- The types involved
web-panel.bridge.src.normalizers.game-status→web-panel.protocol.messages.GameStatusPayload
- Direction
- web-panel.bridge.src.normalizers uses web-panel.protocol.messages, so a change to web-panel.protocol.messages can break web-panel.bridge.src.normalizers, while a change to web-panel.bridge.src.normalizers can't break web-panel.protocol.messages.
- Position
- Below the diagonal: web-panel.bridge.src.normalizers uses a module listed above it, which is the healthy direction.
25→17 web-panel.src.library.model uses web-panel.protocol.messages✕
- Connections
- 1 pair of types, where a type in web-panel.src.library.model uses a type in web-panel.protocol.messages.
- The types involved
web-panel.src.library.model.games→web-panel.protocol.messages.InstalledAppSummary
- Direction
- web-panel.src.library.model uses web-panel.protocol.messages, so a change to web-panel.protocol.messages can break web-panel.src.library.model, while a change to web-panel.src.library.model can't break web-panel.protocol.messages.
- Position
- Below the diagonal: web-panel.src.library.model uses a module listed above it, which is the healthy direction.
26→17 web-panel.src.remote-session uses web-panel.protocol.messages✕
- Connections
- 3 pairs of types, where a type in web-panel.src.remote-session uses a type in web-panel.protocol.messages.
- The types involved
web-panel.src.remote-session.remote-session.protocol→web-panel.protocol.messages.IncomingMessageweb-panel.src.remote-session.use-remote-session→web-panel.protocol.messages.CheatSchemaweb-panel.src.remote-session.use-remote-session→web-panel.protocol.messages.InstalledAppSummary
- Direction
- web-panel.src.remote-session uses web-panel.protocol.messages, so a change to web-panel.protocol.messages can break web-panel.src.remote-session, while a change to web-panel.src.remote-session can't break web-panel.protocol.messages.
- Position
- Below the diagonal: web-panel.src.remote-session uses a module listed above it, which is the healthy direction.
26→18 web-panel.src.remote-session uses web-panel.src.remote-session.remote-session_reducer✕
- Connections
- 1 pair of types, where a type in web-panel.src.remote-session uses a type in web-panel.src.remote-session.remote-session_reducer.
- The types involved
web-panel.src.remote-session.remote-session.reducer→web-panel.src.remote-session.remote-session_reducer.RemoteSessionAction
- Direction
- web-panel.src.remote-session uses web-panel.src.remote-session.remote-session_reducer, so a change to web-panel.src.remote-session.remote-session_reducer can break web-panel.src.remote-session, while a change to web-panel.src.remote-session can't break web-panel.src.remote-session.remote-session_reducer.
- Position
- Below the diagonal: web-panel.src.remote-session uses a module listed above it, which is the healthy direction.
27→17 web-panel.src.remote-session.remote-session_client uses web-panel.protocol.messages✕
- Connections
- 1 pair of types, where a type in web-panel.src.remote-session.remote-session_client uses a type in web-panel.protocol.messages.
- The types involved
web-panel.src.remote-session.remote-session_client.RemoteSessionClient→web-panel.protocol.messages.OutgoingMessage
- Direction
- web-panel.src.remote-session.remote-session_client uses web-panel.protocol.messages, so a change to web-panel.protocol.messages can break web-panel.src.remote-session.remote-session_client, while a change to web-panel.src.remote-session.remote-session_client can't break web-panel.protocol.messages.
- Position
- Below the diagonal: web-panel.src.remote-session.remote-session_client uses a module listed above it, which is the healthy direction.
28→17 web-panel.src.trainer.controls uses web-panel.protocol.messages✕
- Connections
- 1 pair of types, where a type in web-panel.src.trainer.controls uses a type in web-panel.protocol.messages.
- The types involved
web-panel.src.trainer.controls.SelectionControl→web-panel.protocol.messages.CheatOption
- Direction
- web-panel.src.trainer.controls uses web-panel.protocol.messages, so a change to web-panel.protocol.messages can break web-panel.src.trainer.controls, while a change to web-panel.src.trainer.controls can't break web-panel.protocol.messages.
- Position
- Below the diagonal: web-panel.src.trainer.controls uses a module listed above it, which is the healthy direction.
29→17 web-panel.src.trainer.model uses web-panel.protocol.messages✕
- Connections
- 5 pairs of types, where a type in web-panel.src.trainer.model uses a type in web-panel.protocol.messages.
- The types involved
web-panel.src.trainer.model.categories→web-panel.protocol.messages.CheatSchemaweb-panel.src.trainer.model.categories→web-panel.protocol.messages.TrainerSummaryweb-panel.src.trainer.model.values→web-panel.protocol.messages.CheatOptionweb-panel.src.trainer.model.values→web-panel.protocol.messages.CheatOptionLikeweb-panel.src.trainer.model.values→web-panel.protocol.messages.CheatSchema
- Direction
- web-panel.src.trainer.model uses web-panel.protocol.messages, so a change to web-panel.protocol.messages can break web-panel.src.trainer.model, while a change to web-panel.src.trainer.model can't break web-panel.protocol.messages.
- Position
- Below the diagonal: web-panel.src.trainer.model uses a module listed above it, which is the healthy direction.
30→17 web-panel.src.trainer.pinned-cheats uses web-panel.protocol.messages✕
- Connections
- 1 pair of types, where a type in web-panel.src.trainer.pinned-cheats uses a type in web-panel.protocol.messages.
- The types involved
web-panel.src.trainer.pinned-cheats.use-pinned-cheats→web-panel.protocol.messages.CheatSchema
- Direction
- web-panel.src.trainer.pinned-cheats uses web-panel.protocol.messages, so a change to web-panel.protocol.messages can break web-panel.src.trainer.pinned-cheats, while a change to web-panel.src.trainer.pinned-cheats can't break web-panel.protocol.messages.
- Position
- Below the diagonal: web-panel.src.trainer.pinned-cheats uses a module listed above it, which is the healthy direction.
31→17 web-panel.src.trainer.ui uses web-panel.protocol.messages✕
- Connections
- 1 pair of types, where a type in web-panel.src.trainer.ui uses a type in web-panel.protocol.messages.
- The types involved
web-panel.src.trainer.ui.CheatTile→web-panel.protocol.messages.CheatSchema
- Direction
- web-panel.src.trainer.ui uses web-panel.protocol.messages, so a change to web-panel.protocol.messages can break web-panel.src.trainer.ui, while a change to web-panel.src.trainer.ui can't break web-panel.protocol.messages.
- Position
- Below the diagonal: web-panel.src.trainer.ui uses a module listed above it, which is the healthy direction.
32→19 AsarSharp uses AsarSharp.AsarFileSystem✕
- Connections
- 4 pairs of types, where a type in AsarSharp uses a type in AsarSharp.AsarFileSystem.
- The types involved
AsarSharp.AsarCreator→AsarSharp.AsarFileSystem.BasicFileInfoAsarSharp.AsarCreator→AsarSharp.AsarFileSystem.CrawledFileTypeAsarSharp.AsarCreator→AsarSharp.AsarFileSystem.FilesystemAsarSharp.AsarExtractor→AsarSharp.AsarFileSystem.FilesystemEntry
- Direction
- AsarSharp uses AsarSharp.AsarFileSystem, so a change to AsarSharp.AsarFileSystem can break AsarSharp, while a change to AsarSharp can't break AsarSharp.AsarFileSystem.
- Position
- Below the diagonal: AsarSharp uses a module listed above it, which is the healthy direction.
33→6 WandEnhancer.Core uses WandEnhancer.Models✕
- Connections
- 3 pairs of types, where a type in WandEnhancer.Core uses a type in WandEnhancer.Models.
- The types involved
WandEnhancer.Core.Enhancer→WandEnhancer.Models.PatchConfigWandEnhancer.Core.Enhancer→WandEnhancer.Models.WeModConfigWandEnhancer.Core.JavaScriptPatchApplier→WandEnhancer.Models.EPatchType
- Direction
- WandEnhancer.Core uses WandEnhancer.Models, so a change to WandEnhancer.Models can break WandEnhancer.Core, while a change to WandEnhancer.Core can't break WandEnhancer.Models.
- Position
- Below the diagonal: WandEnhancer.Core uses a module listed above it, which is the healthy direction.
33→20 WandEnhancer.Core uses WandEnhancer.Core.Patching.Strategies✕
- Connections
- 1 pair of types, where a type in WandEnhancer.Core uses a type in WandEnhancer.Core.Patching.Strategies.
- The types involved
WandEnhancer.Core.Enhancer→WandEnhancer.Core.Patching.Strategies.IPatchStrategy
- Direction
- WandEnhancer.Core uses WandEnhancer.Core.Patching.Strategies, so a change to WandEnhancer.Core.Patching.Strategies can break WandEnhancer.Core, while a change to WandEnhancer.Core can't break WandEnhancer.Core.Patching.Strategies.
- Position
- Below the diagonal: WandEnhancer.Core uses a module listed above it, which is the healthy direction.
34→6 WandEnhancer uses WandEnhancer.Models✕
- Connections
- 2 pairs of types, where a type in WandEnhancer uses a type in WandEnhancer.Models.
- The types involved
WandEnhancer.Program→WandEnhancer.Models.PatchConfigWandEnhancer.Program→WandEnhancer.Models.WeModConfig
- Direction
- WandEnhancer uses WandEnhancer.Models, so a change to WandEnhancer.Models can break WandEnhancer, while a change to WandEnhancer can't break WandEnhancer.Models.
- Position
- Below the diagonal: WandEnhancer uses a module listed above it, which is the healthy direction.
34→33 WandEnhancer uses WandEnhancer.Core✕
- Connections
- 1 pair of types, where a type in WandEnhancer uses a type in WandEnhancer.Core.
- The types involved
WandEnhancer.Program→WandEnhancer.Core.ELogType
- Direction
- WandEnhancer uses WandEnhancer.Core, so a change to WandEnhancer.Core can break WandEnhancer, while a change to WandEnhancer can't break WandEnhancer.Core.
- Position
- Below the diagonal: WandEnhancer uses a module listed above it, which is the healthy direction.
35→6 WandEnhancer.Core.Patching.Content uses WandEnhancer.Models✕
- Connections
- 2 pairs of types, where a type in WandEnhancer.Core.Patching.Content uses a type in WandEnhancer.Models.
- The types involved
WandEnhancer.Core.Patching.Content.AsarContentPatcher→WandEnhancer.Models.EPatchTypeWandEnhancer.Core.Patching.Content.RemotePanelInjector→WandEnhancer.Models.EPatchType
- Direction
- WandEnhancer.Core.Patching.Content uses WandEnhancer.Models, so a change to WandEnhancer.Models can break WandEnhancer.Core.Patching.Content, while a change to WandEnhancer.Core.Patching.Content can't break WandEnhancer.Models.
- Position
- Below the diagonal: WandEnhancer.Core.Patching.Content uses a module listed above it, which is the healthy direction.
35→33 WandEnhancer.Core.Patching.Content uses WandEnhancer.Core✕
- Connections
- 3 pairs of types, where a type in WandEnhancer.Core.Patching.Content uses a type in WandEnhancer.Core.
- The types involved
WandEnhancer.Core.Patching.Content.AsarContentPatcher→WandEnhancer.Core.ELogTypeWandEnhancer.Core.Patching.Content.AsarContentPatcher→WandEnhancer.Core.JavaScriptPatchApplierWandEnhancer.Core.Patching.Content.RemotePanelInjector→WandEnhancer.Core.ELogType
- Direction
- WandEnhancer.Core.Patching.Content uses WandEnhancer.Core, so a change to WandEnhancer.Core can break WandEnhancer.Core.Patching.Content, while a change to WandEnhancer.Core.Patching.Content can't break WandEnhancer.Core.
- Position
- Below the diagonal: WandEnhancer.Core.Patching.Content uses a module listed above it, which is the healthy direction.
36→6 WandEnhancer.Core.Patching.Shared uses WandEnhancer.Models✕
- Connections
- 1 pair of types, where a type in WandEnhancer.Core.Patching.Shared uses a type in WandEnhancer.Models.
- The types involved
WandEnhancer.Core.Patching.Shared.LauncherDeployment→WandEnhancer.Models.WeModConfig
- Direction
- WandEnhancer.Core.Patching.Shared uses WandEnhancer.Models, so a change to WandEnhancer.Models can break WandEnhancer.Core.Patching.Shared, while a change to WandEnhancer.Core.Patching.Shared can't break WandEnhancer.Models.
- Position
- Below the diagonal: WandEnhancer.Core.Patching.Shared uses a module listed above it, which is the healthy direction.
36→20 WandEnhancer.Core.Patching.Shared uses WandEnhancer.Core.Patching.Strategies✕
- Connections
- 1 pair of types, where a type in WandEnhancer.Core.Patching.Shared uses a type in WandEnhancer.Core.Patching.Strategies.
- The types involved
WandEnhancer.Core.Patching.Shared.AuxiliaryCompatibility→WandEnhancer.Core.Patching.Strategies.PatchContext
- Direction
- WandEnhancer.Core.Patching.Shared uses WandEnhancer.Core.Patching.Strategies, so a change to WandEnhancer.Core.Patching.Strategies can break WandEnhancer.Core.Patching.Shared, while a change to WandEnhancer.Core.Patching.Shared can't break WandEnhancer.Core.Patching.Strategies.
- Position
- Below the diagonal: WandEnhancer.Core.Patching.Shared uses a module listed above it, which is the healthy direction.
36→33 WandEnhancer.Core.Patching.Shared uses WandEnhancer.Core✕
- Connections
- 1 pair of types, where a type in WandEnhancer.Core.Patching.Shared uses a type in WandEnhancer.Core.
- The types involved
WandEnhancer.Core.Patching.Shared.LauncherDeployment→WandEnhancer.Core.ELogType
- Direction
- WandEnhancer.Core.Patching.Shared uses WandEnhancer.Core, so a change to WandEnhancer.Core can break WandEnhancer.Core.Patching.Shared, while a change to WandEnhancer.Core.Patching.Shared can't break WandEnhancer.Core.
- Position
- Below the diagonal: WandEnhancer.Core.Patching.Shared uses a module listed above it, which is the healthy direction.
37→20 WandEnhancer.Core.Patching.Strategies.Static uses WandEnhancer.Core.Patching.Strategies✕
- Connections
- 2 pairs of types, where a type in WandEnhancer.Core.Patching.Strategies.Static uses a type in WandEnhancer.Core.Patching.Strategies.
- The types involved
WandEnhancer.Core.Patching.Strategies.Static.StaticStrategy→WandEnhancer.Core.Patching.Strategies.IPatchStrategyWandEnhancer.Core.Patching.Strategies.Static.StaticStrategy→WandEnhancer.Core.Patching.Strategies.PatchContext
- Direction
- WandEnhancer.Core.Patching.Strategies.Static uses WandEnhancer.Core.Patching.Strategies, so a change to WandEnhancer.Core.Patching.Strategies can break WandEnhancer.Core.Patching.Strategies.Static, while a change to WandEnhancer.Core.Patching.Strategies.Static can't break WandEnhancer.Core.Patching.Strategies.
- Position
- Below the diagonal: WandEnhancer.Core.Patching.Strategies.Static uses a module listed above it, which is the healthy direction.
37→33 WandEnhancer.Core.Patching.Strategies.Static uses WandEnhancer.Core✕
- Connections
- 1 pair of types, where a type in WandEnhancer.Core.Patching.Strategies.Static uses a type in WandEnhancer.Core.
- The types involved
WandEnhancer.Core.Patching.Strategies.Static.AuxTrustNeutralizer→WandEnhancer.Core.ELogType
- Direction
- WandEnhancer.Core.Patching.Strategies.Static uses WandEnhancer.Core, so a change to WandEnhancer.Core can break WandEnhancer.Core.Patching.Strategies.Static, while a change to WandEnhancer.Core.Patching.Strategies.Static can't break WandEnhancer.Core.
- Position
- Below the diagonal: WandEnhancer.Core.Patching.Strategies.Static uses a module listed above it, which is the healthy direction.
38→20 WandEnhancer.Core.Patching.Strategies.Supervised uses WandEnhancer.Core.Patching.Strategies✕
- Connections
- 2 pairs of types, where a type in WandEnhancer.Core.Patching.Strategies.Supervised uses a type in WandEnhancer.Core.Patching.Strategies.
- The types involved
WandEnhancer.Core.Patching.Strategies.Supervised.SupervisedStrategy→WandEnhancer.Core.Patching.Strategies.IPatchStrategyWandEnhancer.Core.Patching.Strategies.Supervised.SupervisedStrategy→WandEnhancer.Core.Patching.Strategies.PatchContext
- Direction
- WandEnhancer.Core.Patching.Strategies.Supervised uses WandEnhancer.Core.Patching.Strategies, so a change to WandEnhancer.Core.Patching.Strategies can break WandEnhancer.Core.Patching.Strategies.Supervised, while a change to WandEnhancer.Core.Patching.Strategies.Supervised can't break WandEnhancer.Core.Patching.Strategies.
- Position
- Below the diagonal: WandEnhancer.Core.Patching.Strategies.Supervised uses a module listed above it, which is the healthy direction.
38→33 WandEnhancer.Core.Patching.Strategies.Supervised uses WandEnhancer.Core✕
- Connections
- 1 pair of types, where a type in WandEnhancer.Core.Patching.Strategies.Supervised uses a type in WandEnhancer.Core.
- The types involved
WandEnhancer.Core.Patching.Strategies.Supervised.SupervisedStrategy→WandEnhancer.Core.ELogType
- Direction
- WandEnhancer.Core.Patching.Strategies.Supervised uses WandEnhancer.Core, so a change to WandEnhancer.Core can break WandEnhancer.Core.Patching.Strategies.Supervised, while a change to WandEnhancer.Core.Patching.Strategies.Supervised can't break WandEnhancer.Core.
- Position
- Below the diagonal: WandEnhancer.Core.Patching.Strategies.Supervised uses a module listed above it, which is the healthy direction.
39→6 WandEnhancer.Core.Services uses WandEnhancer.Models✕
- Connections
- 2 pairs of types, where a type in WandEnhancer.Core.Services uses a type in WandEnhancer.Models.
- The types involved
WandEnhancer.Core.Services.AppSettings→WandEnhancer.Models.PatchConfigWandEnhancer.Core.Services.WatcherAutostart→WandEnhancer.Models.WeModConfig
- Direction
- WandEnhancer.Core.Services uses WandEnhancer.Models, so a change to WandEnhancer.Models can break WandEnhancer.Core.Services, while a change to WandEnhancer.Core.Services can't break WandEnhancer.Models.
- Position
- Below the diagonal: WandEnhancer.Core.Services uses a module listed above it, which is the healthy direction.
39→33 WandEnhancer.Core.Services uses WandEnhancer.Core✕
- Connections
- 2 pairs of types, where a type in WandEnhancer.Core.Services uses a type in WandEnhancer.Core.
- The types involved
WandEnhancer.Core.Services.UpdateWatcherService→WandEnhancer.Core.ELogTypeWandEnhancer.Core.Services.WatcherAutostart→WandEnhancer.Core.ELogType
- Direction
- WandEnhancer.Core.Services uses WandEnhancer.Core, so a change to WandEnhancer.Core can break WandEnhancer.Core.Services, while a change to WandEnhancer.Core.Services can't break WandEnhancer.Core.
- Position
- Below the diagonal: WandEnhancer.Core.Services uses a module listed above it, which is the healthy direction.
40→6 WandEnhancer.View.MainWindow uses WandEnhancer.Models✕
- Connections
- 1 pair of types, where a type in WandEnhancer.View.MainWindow uses a type in WandEnhancer.Models.
- The types involved
WandEnhancer.View.MainWindow.MainWindowVm→WandEnhancer.Models.WeModConfig
- Direction
- WandEnhancer.View.MainWindow uses WandEnhancer.Models, so a change to WandEnhancer.Models can break WandEnhancer.View.MainWindow, while a change to WandEnhancer.View.MainWindow can't break WandEnhancer.Models.
- Position
- Below the diagonal: WandEnhancer.View.MainWindow uses a module listed above it, which is the healthy direction.
40→7 WandEnhancer.View.MainWindow uses WandEnhancer.ReactiveUICore✕
- Connections
- 2 pairs of types, where a type in WandEnhancer.View.MainWindow uses a type in WandEnhancer.ReactiveUICore.
- The types involved
WandEnhancer.View.MainWindow.MainWindowVm→WandEnhancer.ReactiveUICore.ObservableObjectWandEnhancer.View.MainWindow.MainWindowVm→WandEnhancer.ReactiveUICore.RelayCommand
- Direction
- WandEnhancer.View.MainWindow uses WandEnhancer.ReactiveUICore, so a change to WandEnhancer.ReactiveUICore can break WandEnhancer.View.MainWindow, while a change to WandEnhancer.View.MainWindow can't break WandEnhancer.ReactiveUICore.
- Position
- Below the diagonal: WandEnhancer.View.MainWindow uses a module listed above it, which is the healthy direction.
40→33 WandEnhancer.View.MainWindow uses WandEnhancer.Core✕
- Connections
- 2 pairs of types, where a type in WandEnhancer.View.MainWindow uses a type in WandEnhancer.Core.
- The types involved
WandEnhancer.View.MainWindow.LogEntry→WandEnhancer.Core.ELogTypeWandEnhancer.View.MainWindow.MainWindowVm→WandEnhancer.Core.ELogType
- Direction
- WandEnhancer.View.MainWindow uses WandEnhancer.Core, so a change to WandEnhancer.Core can break WandEnhancer.View.MainWindow, while a change to WandEnhancer.View.MainWindow can't break WandEnhancer.Core.
- Position
- Below the diagonal: WandEnhancer.View.MainWindow uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 13 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
Roadmap
Top priorities: Resolve the 8 EmptyCatchBlock finding(s) in Explicit Debt — start with REDACTED (2), SettingsManager.cs (2), LocalizationManager.cs; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the `catch` blocks that emit nothing — a discarded exception is the failure the user cannot describe and you cannot reproduce; Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 EmptyCatchBlock finding(s) in Explicit Debt — start with REDACTED (2), SettingsManager.cs (2), LocalizationManager.cs. | +5.1 pts | Low | Explicit Debt |
| Resolve the 1 Build failed finding(s) in Solution Shape. | +3.6 pts | Low | Solution Shape |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the `catch` blocks that emit nothing — a discarded exception is the failure the user cannot describe and you cannot reproduce. | +4.8 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.8 pts | Medium | Security & performance tooling |
| Resolve the 3 No assertions finding(s) in Test Quality — start with runtime.integration.test.ts (3). | +1.9 pts | Low | Test Quality |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +3.8 pts | Medium | Type Safety |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.9 pts | Low | ADR Quality |
| Resolve the 5 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (5). | +1.8 pts | Low | Comment Value |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.8 | Slop | Explicit Debt: EmptyCatchBlock |
| REDACTED | 3.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| WandEnhancer/Utils/WeModInstalls.cs | 6.1 | Mixed | Explicit Debt: EmptyCatchBlock |
| WandEnhancer/Core/Services/SettingsManager.cs | 6.4 | Mixed | Explicit Debt: EmptyCatchBlock |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| WandEnhancer/Core/Patching/Strategies/Static/DotNetImage.cs | 7.1 | Mixed | Cyclomatic Complexity: DotNetImage.HasStatusSignature (cyclomatic 17) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| WandEnhancer/Core/Patching/Strategies/Supervised/SupervisedStrategy.cs | 7.4 | Mixed | Cyclomatic Complexity: SupervisedStrategy.ClearFuseInNewProcesses (cyclomatic 18) |
| web-panel/bridge/src/runtime.integration.test.ts | 7.4 | Mixed | Test Quality: No assertions: rejects a browser WebSocket from a different origin |
| WandEnhancer/Core/Services/LocalizationManager.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| WandEnhancer/View/MainWindow/MainWindowVm.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| AsarSharp/AsarFileSystem/FileSystem.cs | 7.8 | Mixed | Cyclomatic Complexity: Filesystem.SearchNodeFromDirectory (cyclomatic 17) |
| AsarSharp/AsarFileSystem/FileSystemCrawler.cs | 8.5 | Near-clean | Cognitive Complexity: FileSystemCrawler.CrawlFileSystem (cognitive 19) |
| WandEnhancer/Core/Patching/Content/AsarContentPatcher.cs | 8.5 | Near-clean | Cognitive Complexity: AsarContentPatcher.Patch (cognitive 17) |
| AsarSharp/AsarExtractor.cs | 8.5 | Near-clean | Cognitive Complexity: AsarExtractor.ExtractAll (cognitive 17) |
| WandEnhancer/Core/Patching/Strategies/Static/AuxTrustNeutralizer.cs | 8.5 | Near-clean | Cognitive Complexity: AuxTrustNeutralizer.Neutralize (cognitive 16) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey 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. All 64 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 64 dimensions across the health lenses
- 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, 99 of 117 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 or a scanner, 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 |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ 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 |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'WandEnhancer/WandEnhancer.csproj' with message: This project references NuGet package(s) that are missing on this computer. Enable NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105.The missing file is ..\packages\ILRepack.2.0.41\build….
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `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). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `WandEnhancer/Patches/devtools-f12.js`, `WandEnhancer/Patches/remote-bridge-boot.js`, `WandEnhancer/Patches/remote-bridge-renderer.js`, `WandEnhancer/Patches/remote-bridge-sync.js`, `WandEnhancer/Patches/remote-bridge-value-delta.js`, … (+1 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do 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 — an in-process token-stream comparison over sliding windows, with type-aware normalization — so 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SupervisedStrategy.ClearFuseInNewProcesses at 18.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SupervisedStrategy.ClearFuseInNewProcesses (cyclomatic 18), SupervisedStrategy.Run (cyclomatic 17), DotNetImage.HasStatusSignature (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 9.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
9 method(s) exceeded the cognitive complexity threshold of 15; the worst was Filesystem.SearchNodeFromDirectory at 28.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cognitive Complexity — start with Filesystem.SearchNodeFromDirectory (cognitive 28), SupervisedStrategy.ClearFuseInNewProcesses (cognitive 23), DotNetImage.FindFuseValidationBodyOffsets (cognitive 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 9 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
2 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 2 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with WeModInstalls.cs, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (28 corresponding lines) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with Pickle.cs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 18 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 3 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 54 tests.
What to do
- Resolve the 3 No assertions finding(s) in Test Quality — start with runtime.integration.test.ts (3). — One of this dimension's main actionable groups (3 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in web-panel/ (67 tests)): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 0 packages use a banned license. The depth of this set was not established for this repository: the graded packages are what this pass resolved, and no lockfile was read, so it is not certified to be the full transitive closure. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: WandEnhancer/Core/Patching/Strategies/Supervised/SupervisedStrategy.cs (9×18=162) Repeated repair below the complexity floor: REDACTED (11 of 17 changes were fixes); REDACTED (3 of 4 changes were fixes); AsarSharp/AsarFileSystem/Disk.cs (3 of 4 changes were fixes)
What to do
- Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with REDACTED, REDACTED, Disk.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with SupervisedStrategy.cs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
14 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is WandEnhancer/Core/Patching/Strategies/Supervised/SupervisedStrategy.cs. Counted over 34 of the 61 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
8 deducted debt markers + unmeasured dead symbols across 6402 LoC in the .NET projects (1.0/KLoC) → score 8.1. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 8 EmptyCatchBlock finding(s) in Explicit Debt — start with REDACTED (2), SettingsManager.cs (2), LocalizationManager.cs. — One of this dimension's main actionable groups (8 issue-level).
D18 · Solution Shape
2 projects, 62 source files, 6402 hand-written lines of code (6402 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 63 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 1 inter-project edges (build failed).
What to do
- Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 3 unit(s).
D20 · ADR Quality
No architecture decision records were 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).
D24 · Comment Value
12 of 122 judged comments only repeat the code they sit on (9.8 %). 4 comment(s) in another language or script were not judged.
What to do
- Resolve the 5 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (5). — One of this dimension's main actionable groups (5 recommendation-level).
D26 · Project Cohesion
0 of 2 projects flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
14 finding(s): 0 critical, 11 high, 3 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 6 file(s) — `WandEnhancer/Patches/devtools-f12.js` (line 1), `WandEnhancer/Patches/remote-bridge-boot.js` (line 1), `WandEnhancer/Patches/remote-bridge-renderer.js` (line 1), `WandEnhancer/Patches/remote-bridge-sync.js` (line 1), `WandEnhancer/Patches/remote-bridge-value-delta.js` (line 1), … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 3 high, 1 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: `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). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
1 of 34 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is WandEnhancer/View/Controls/PopupHost.xaml.cs. Counted over 34 of the 61 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `LauncherLog` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_path; e.g. `_path` at line 32). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — WandEnhancer/Core/LauncherLog.cs:10
- `LocalizationManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_englishBaseDictionary, _currentLanguage, _activeLocaleDictionary; e.g. `_englishBaseDictionary` at line 57). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — WandEnhancer/Core/Services/LocalizationManager.cs:11
What to do
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces WandEnhancer.Core ↔ WandEnhancer.Core.Patching.Strategies depend on each other. The lightest dependency in the cycle is WandEnhancer.Core → WandEnhancer.Core.Patching.Strategies (WandEnhancer.Core.Enhancer → WandEnhancer.Core.Patching.Strategies.IPatchStrategy, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — REDACTED:10
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
C2 · Access Controls
- Authorization IS enforced here (by imperative guard methods that throw on violation) — this is NOT a claim that the code is unprotected. What's missing is a NAMED rule set: the guards encode the access rules inline, so the rules can't be listed, reviewed or tested apart from the call sites that apply them. Recommendation, not a defect.
What to do
- Name the access rules — give each one a named predicate/policy object your guards consult, so the rule set can be reviewed and unit-tested independently of the call sites that enforce it.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 2 of 2 have no README of their own, in their folder or in their family's project (`WandEnhancer`, `AsarSharp`).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, 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.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the `catch` blocks that emit nothing — a discarded exception is the failure the user cannot describe and you cannot reproduce.
- For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `AsarSharp/packages.config` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — AsarSharp/packages.config:3
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — 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.
P4 · Deployment & Rollback
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 8 plain JS — the untyped files are WandEnhancer/Patches/devtools-f12.js, WandEnhancer/Patches/disable-native-pairing.js, WandEnhancer/Patches/disable-updates.js, WandEnhancer/Patches/remote-bridge-reset.js, WandEnhancer/Patches/remote-bridge-sync.js, WandEnhancer/Patches/remote-bridge-value-delta.js (+2 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 25 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/diagnostics/capture-trainer-launch.js:3
- snapshot has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/diagnostics/capture-trainer-launch.js:43
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
R7 · Dead Code
- 6 file(s) (~607 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — web-panel/bridge
- Unreachable from the 8 application, 0 tooling and 17 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (8 application, 0 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — scripts/diagnostics/capture-trainer-launch.js
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — web-panel/src/shared/ui/Drawer.test.tsx:4
- Only test files import it (first: web-panel/src/app/ui/session-states.test.tsx:1) — move it to devDependencies. — web-panel/package.json:27
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Cryptographic Hygiene
- MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — WandEnhancer/Core/Services/UpdateWatcherService.cs:228
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
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. (×4) — WandEnhancer/View/MainWindow/MainWindow.xaml.cs:49, WandEnhancer/View/MainWindow/MainWindowVm.cs:126, WandEnhancer/View/MainWindow/MainWindowVm.cs:180, …
What to do
- async void method: OnDrop
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X2 · Cancellation propagation
- Only 0/2 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. (×2) — WandEnhancer/View/MainWindow/MainWindowVm.cs:148, WandEnhancer/View/MainWindow/MainWindowVm.cs:180
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
- The guard on line 41 rejects `relativeTo` and line 42 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(relativeTo)` is true of a value that is NOT null: it is satisfied by an EMPTY `relativeTo`, and on that path `relativeTo` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — REDACTED:42
- The guard on line 43 rejects `path` and line 44 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(path)` is true of a value that is NOT null: it is satisfied by an EMPTY `path`, and on that path `path` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — REDACTED:44
What to do
- Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
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. (×8) — REDACTED:298, REDACTED:328, WandEnhancer/Core/Services/LocalizationManager.cs:159, …
- `catch (Exception) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — WandEnhancer/Core/LauncherLog.cs:35
- `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — WandEnhancer/Utils/WeModInstalls.cs:111
- `catch (UnauthorizedAccessException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — AsarSharp/AsarFileSystem/FileSystemCrawler.cs:108
What to do
- Swallowed exception (empty catch)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 41% | Weak — gated by D18, R1, X1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 74% | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 61% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 35% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 62% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 61 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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.
- 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.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (6,402 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — the repository wires up no coverage collector for `--collect:"XPlat Code Coverage"` to use; the JavaScript/TypeScript half could not be measured — web-panel/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens 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 lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- 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) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, 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 — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — 17 test file(s) reach none of 7 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X5 Nullable reference types — no NRT-eligible projects
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 23 finding(s)
- EmptyCatchBlock REDACTED:298
- EmptyCatchBlock REDACTED:328
- EmptyCatchBlock WandEnhancer/Core/Services/LocalizationManager.cs:159
- EmptyCatchBlock WandEnhancer/Core/Services/SettingsManager.cs:37
- EmptyCatchBlock WandEnhancer/Core/Services/SettingsManager.cs:51
- EmptyCatchBlock REDACTED:75
- EmptyCatchBlock WandEnhancer/Utils/WeModInstalls.cs:135
- EmptyCatchBlock WandEnhancer/View/MainWindow/MainWindowVm.cs:70
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle REDACTED:10
- REDACTED
- Unlisted import 'react' web-panel/src/shared/ui/Drawer.test.tsx:4
Serious — 61 finding(s)
- Swallowed exception (empty catch) REDACTED:298
- Swallowed exception (empty catch) REDACTED:328
- Swallowed exception (empty catch) WandEnhancer/Core/Services/LocalizationManager.cs:159
- Swallowed exception (empty catch) WandEnhancer/Core/Services/SettingsManager.cs:37
- Swallowed exception (empty catch) WandEnhancer/Core/Services/SettingsManager.cs:51
- Swallowed exception (empty catch) REDACTED:75
- Swallowed exception (empty catch) WandEnhancer/Utils/WeModInstalls.cs:135
- Swallowed exception (empty catch) WandEnhancer/View/MainWindow/MainWindowVm.cs:70
- async void method: OnDrop WandEnhancer/View/MainWindow/MainWindow.xaml.cs:49
- async void method: OnFolderPathSelection WandEnhancer/View/MainWindow/MainWindowVm.cs:126
- async void method: OnBackupRestoring WandEnhancer/View/MainWindow/MainWindowVm.cs:180
- async void method: OnRescanInstall WandEnhancer/View/MainWindow/MainWindowVm.cs:253
- No assertions: rejects a browser WebSocket from a different origin web-panel/bridge/src/runtime.integration.test.ts:46
- No assertions: allows the local Vite panel to connect to the loopback bridge web-panel/bridge/src/runtime.integration.test.ts:59
- No assertions: closes an oversized WebSocket frame without buffering its payload web-panel/bridge/src/runtime.integration.test.ts:72
- Repeated repair: REDACTED REDACTED:174
- Repeated repair: REDACTED REDACTED:25
- Repeated repair: AsarSharp/AsarFileSystem/Disk.cs AsarSharp/AsarFileSystem/Disk.cs:78
- Swallowed exception (caught, then discarded) WandEnhancer/Core/LauncherLog.cs:35
- Swallowed exception (caught, then discarded) WandEnhancer/Utils/WeModInstalls.cs:111
- Swallowed exception (caught, then discarded) AsarSharp/AsarFileSystem/FileSystemCrawler.cs:108
- Process-global static state: LauncherLog WandEnhancer/Core/LauncherLog.cs:10
- Process-global static state: LocalizationManager WandEnhancer/Core/Services/LocalizationManager.cs:11
- REDACTED
- REDACTED
- Edited copy of a member (11 corresponding lines) WandEnhancer/Utils/WeModInstalls.cs:169
- Edited copy of a member (11 corresponding lines) REDACTED:40
- Async method without CancellationToken: PickInstallAsync WandEnhancer/View/MainWindow/MainWindowVm.cs:148
- Async method without CancellationToken: OnBackupRestoring WandEnhancer/View/MainWindow/MainWindowVm.cs:180
- Argument guard throws the exception its own condition disproves REDACTED:42
- Argument guard throws the exception its own condition disproves REDACTED:44
- SupervisedStrategy.ClearFuseInNewProcesses (cyclomatic 18) WandEnhancer/Core/Patching/Strategies/Supervised/SupervisedStrategy.cs:256
- SupervisedStrategy.Run (cyclomatic 17) WandEnhancer/Core/Patching/Strategies/Supervised/SupervisedStrategy.cs:54
- DotNetImage.HasStatusSignature (cyclomatic 17) WandEnhancer/Core/Patching/Strategies/Static/DotNetImage.cs:118
- Filesystem.SearchNodeFromDirectory (cyclomatic 17) AsarSharp/AsarFileSystem/FileSystem.cs:36
- Hotspot: WandEnhancer/Core/Patching/Strategies/Supervised/SupervisedStrategy.cs WandEnhancer/Core/Patching/Strategies/Supervised/SupervisedStrategy.cs:256
- Build failed
- Filesystem.SearchNodeFromDirectory (cognitive 28) AsarSharp/AsarFileSystem/FileSystem.cs:36
- SupervisedStrategy.ClearFuseInNewProcesses (cognitive 23) WandEnhancer/Core/Patching/Strategies/Supervised/SupervisedStrategy.cs:256
- DotNetImage.FindFuseValidationBodyOffsets (cognitive 19) WandEnhancer/Core/Patching/Strategies/Static/DotNetImage.cs:85
- FileSystemCrawler.CrawlFileSystem (cognitive 19) AsarSharp/AsarFileSystem/FileSystemCrawler.cs:46
- AsarContentPatcher.Patch (cognitive 17) WandEnhancer/Core/Patching/Content/AsarContentPatcher.cs:27
- DotNetImage.FindAsarValidationBodyOffsets (cognitive 17) WandEnhancer/Core/Patching/Strategies/Static/DotNetImage.cs:54
- AsarExtractor.ExtractAll (cognitive 17) AsarSharp/AsarExtractor.cs:16
- DotNetImage.HasStatusSignature (cognitive 16) WandEnhancer/Core/Patching/Strategies/Static/DotNetImage.cs:118
- AuxTrustNeutralizer.Neutralize (cognitive 16) WandEnhancer/Core/Patching/Strategies/Static/AuxTrustNeutralizer.cs:16
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (28 corresponding lines) REDACTED:277
- Edited copy of a member (6 corresponding lines) AsarSharp/PickleTools/Pickle.cs:204
- Duplicated block (11 lines × 2) WandEnhancer/Core/Patching/Strategies/Static/DotNetImage.cs:65
- Duplicated block (8 lines × 2) REDACTED:53
- Coverage not measured — .NET and JavaScript/TypeScript suite
- No structured logging
- Type Safety
- Complex function (anonymous) (cyclomatic 25, cognitive 42) scripts/diagnostics/capture-trainer-launch.js:3
- Complex function snapshot (cyclomatic 11, cognitive 9) scripts/diagnostics/capture-trainer-launch.js:43
- Dead file (~73 LoC) scripts/diagnostics/capture-trainer-launch.js
- Weak hash algorithm WandEnhancer/Core/Services/UpdateWatcherService.cs:228
- NuGet dependencies are not locked
Minor — 33 finding(s)
- Duplicated predicate REDACTED:168
- Duplicated predicate WandEnhancer/Utils/WeModInstalls.cs:33
- Duplicated predicate WandEnhancer/Core/Patching/Strategies/Supervised/SupervisedStrategy.cs:179
- Duplicated predicate web-panel/bridge/src/server.ts:77
- Duplicated predicate web-panel/bridge/src/normalizers/index.ts:19
- Duplicated predicate web-panel/bridge/scripts/default/installed-apps-sync/runtime.js:267
- Duplicated predicate web-panel/bridge/scripts/default/installed-apps-sync/runtime.js:4
- Duplicated predicate web-panel/bridge/scripts/default/installed-apps-sync/runtime.js:51
- Duplicated predicate web-panel/bridge/dev-server.mjs:94
- Duplicated predicate WandEnhancer/Core/Services/UpdateWatcherService.cs:136
- redundant comment AsarSharp/Properties/AssemblyInfo.cs:4
- redundant comment AsarSharp/Properties/AssemblyInfo.cs:16
- redundant comment AsarSharp/Properties/AssemblyInfo.cs:21
- redundant comment AsarSharp/Properties/AssemblyInfo.cs:24
- redundant comment WandEnhancer/Properties/AssemblyInfo.cs:7
- Silent fallback default in catch WandEnhancer/Core/Patching/Strategies/Supervised/SupervisedStrategy.cs:179
- Silent fallback default in catch REDACTED:201
- No named authorization policies
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Orphaned files with no living knowledge
- Orphaned file WandEnhancer/View/Controls/PopupHost.xaml.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:6
- No dependency-update automation AsarSharp/packages.config:3
- Test-only dependency '@lingui/core' in production deps web-panel/package.json:27
- Not all async methods take a CancellationToken
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5fe44a06a62a4a9cba67090cedaffb37/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5fe44a06a62a4a9cba67090cedaffb37/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude web-panel . | 14 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: `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). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 4 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 6 file(s) — `WandEnhancer/Patches/devtools-f12.js`, `WandEnhancer/Patches/remote-bridge-boot.js`, `WandEnhancer/Patches/remote-bridge-renderer.js`, `WandEnhancer/Patches/remote-bridge-sync.js`, `WandEnhancer/Patches/remote-bridge-value-delta.js`, … (+1 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | — |
| 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 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |