Public report — SolidEdgeHousekeeper, published 8 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
469findings with an exact file:lineof 476 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
34/90dimensions across the health lenses · 2 projects — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
rmcanany/SolidEdgeHousekeeper carries serious gaps (35%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
The area that most needs attention is Readiness (17%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Architecture (41%) is the next concern — the code resists change, so features cost more over time.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); ILogger (or Serilog) and log at meaningful points across… (Observability); 1 No automated tests finding(s) in Code Coverage (Code Coverage).
For scale: — (~0 production lines); rebuilding it from scratch would take roughly — (—). Approximate, ±~30%.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 1 No automated tests finding(s) in Code Coverage.
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a CI workflow that builds and runs the test suite on every push/PR.
At a glance — Code Health · 73% · Adequate · gated by D1, D2, D18
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A02:2021 — Cryptographic Failures
1
Medium
Roadmap
First, establish a continuous integration workflow to automatically build and test every change. Next, implement structured logging across all services to improve observability and debugging capabilities. Then, address the lack of automated tests by resolving the identified coverage gaps and ensuring tests are properly distributed. Finally, refactor the codebase to introduce clear architectural boundaries, such as separating features or layers, to improve maintainability.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No automated tests finding(s) in Code Coverage.
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
Per-file score 0–10 — a quality signature. Of 66 files carrying findings, judged against the Production bar: 26% slop · 62% mixed · 12% near-clean.
File
Score
Band
Worst signal
My Project/TaskUpdateBlocks.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/Form_Main.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsPreferences.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsCommon.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskEditInteractively.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskSaveDrawingAs.vb
1.3
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskCheckDrawings.vb
1.3
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskUpdateDrawingStylesFromTemplate.vb
1.9
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskBreakLinks.vb
2.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskShowHideConstructions.vb
2.3
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsTopLevelAssembly.vb
2.4
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskUpdateDrawingViews.vb
2.7
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsSEApp.vb
3.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/FormExpressionEditor.vb
3.2
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskPrint.vb
3.3
Slop
Explicit Debt: EmptyCatchBlock
My Project/HCPropertiesData.vb
3.4
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsFileList.vb
3.4
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskSaveModelAs.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
My Project/TaskCheckInterference.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
My Project/UtilsMaterials.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 31 of 34 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 34 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 469 of 476 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D31 IaC & Container Security — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D32 Data Compliance (PII/GDPR) — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D33 JS/npm Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D36 Supply-chain Provenance & Signing — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D37 Vulnerability-disclosure Policy — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D38 OSV Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (EF migration scaffolds, *.Designer.cs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only; the generated footprint is reported separately under Solution Shape.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the suite (`dotnet test --collect`) inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (EF migrations, designer files, snapshots) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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 the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
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.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 59 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 UtilsMaterials.GetFeatureFaceStyle (cyclomatic 118) finding(s) in Cyclomatic Complexity — start with UtilsMaterials.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PropertyData.New.ctor (cyclomatic 81) finding(s) in Cyclomatic Complexity — start with HCPropertiesData.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TaskUpdateBlocks.ProcessInternal (cyclomatic 54) finding(s) in Cyclomatic Complexity — start with TaskUpdateBlocks.vb. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 148 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 TaskUpdateBlocks.ProcessInternal (cognitive 219) finding(s) in Cognitive Complexity — start with TaskUpdateBlocks.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TaskCheckFilename.ProcessInternal (cognitive 194) finding(s) in Cognitive Complexity — start with TaskCheckFilename.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TaskEditProperties.DoFindReplace (cognitive 144) finding(s) in Cognitive Complexity — start with TaskEditProperties.vb. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes6.1 / 10Adequate✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 28 ClassTooLong finding(s) in God Classes — start with FormExpressionEditor.vb, FormPropertyFilter.vb, FormPropertyInputEditor.vb. — One of this dimension's main actionable groups (28 warning-level).
Resolve the 22 FileTooLong finding(s) in God Classes — start with FormExpressionEditor.vb, Form_Main.vb, HCPropertiesData.vb. — One of this dimension's main actionable groups (22 warning-level).
Resolve the 3 TooManyMethods finding(s) in God Classes — start with Form_Main.vb, HCStructuredStorageDoc.vb, UtilsPreferences.vb. — One of this dimension's main actionable groups (3 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
+ 30 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with TaskCreateDrawingOfFlatPattern.vb (2), TaskSaveDrawingAs.vb (2), FormPropertyFilter.vb. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 7 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with TaskCheckDrawings.vb (2), TaskSaveDrawingAs.vb (2), FormPropertyFilter.vb. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 7 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with TaskCreateDrawingOfFlatPattern.vb (2), FormPropertyInputEditor.vb, TaskCheckInterference.vb. — One of this dimension's main actionable groups (7 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 28 Low cohesion finding(s) in Cohesion (LCOM4) — start with HCIsolatedTaskProxy.vb, Task.vb, TaskBreakLinks.vb. — One of this dimension's main actionable groups (28 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
No automated tests — the solution has no test code.
No automated tests
What to do
Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution0.0 / 10Critical✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
Resolve the 72 EmptyCatchBlock finding(s) in Explicit Debt — start with UtilsSEApp.vb (9), TaskEditInteractively.vb (7), UtilsCommon.vb (7). — One of this dimension's main actionable groups (72 issue-level).
Resolve the 3 XxxComment finding(s) in Explicit Debt — start with UtilsPreferences.vb (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 TodoComment finding(s) in Explicit Debt — start with HCStructuredStorageDoc.vb, TaskUpdateBlocks.vb. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
2 projects, 0 .cs files, 36376 hand-written lines of code (36376 production / 0 test), plus 10556 generated (EF migrations / designer / snapshots, excluded from quality), 0 inter-project edges (build failed).
Shell project: Housekeeper · ×2Housekeeper.vbproj
Build did not complete in the analyzer
What to do
Resolve the 2 Shell project finding(s) in Solution Shape — start with Housekeeper.vbproj, HousekeeperCLI.vbproj. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The README is a single file (README.md) with no accompanying architecture or design documentation and no XML documentation coverage. The body contains only credits information — sponsors, contributors, beta testers, and a legal disclaimers section — plus an open details panel that clips mid-sentence before any real content appears. There are no instructions for installing the project, running tests, or using the API; the README is essentially a one-line credit banner with no value.
No installation/run commands and no usage description exist in the visible text.README.md
Resolve the 1 No installation/run commands and no usage description exist in the… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
1 of 2 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Rotate the exposed credentials — git history can't be un-committed
What to do
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
Resolve the 10 Change coupling finding(s) in Change Coupling — start with Form_Main.vb (6), FormExpressionEditor.vb, FormPropertyPicker.vb. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
~36.4k production LoC (163 types) across 2 project(s) / 6 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
What to do
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 1 of 2 project(s) that lack one — worth up to 1 pts.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem/Roslyn scan: CodeQL, Dependabot, secret-scanning, and BenchmarkDotNet presence in pipelines and projects. Exhaustive, deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 57 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — no source files detected — code composition not applicable
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — no csproj graph available
AX4 Dependency direction — no csproj graph available
AX6 Interface segregation — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D10 Test Quality — No tests in the analyzed solution to assess for quality.
D11 Test Reliability — Test reliability not included
D14 License Compliance — license scan produced no result — the tool ran but its JSON output could not be parsed; the offline NuGet fallback resolved nothing
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — At only 36k LoC across two projects the codebase is small and single-purpose despite the absence of declared bounded contexts.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
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, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D38 OSV Dependency Vulnerabilities — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — not run — 0/3 markers found
ED1 Event-Driven — not run — 0/3 markers found
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not run — 0/3 markers found
IC1 Incompleteness & stubs — no C# methods found
P12 CI test-gate honesty — no CI workflow found
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — run tests with `--collect:"XPlat Code Coverage"` (or in CI) to enable this cross-layer check
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — no data
X2 Cancellation propagation — no async methods found
X5 Nullable reference types — no NRT-eligible projects
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Low cohesion: UtilsCommon (LCOM4 16) My Project/UtilsCommon.vb:9— UtilsCommon's methods form 16 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: Task (LCOM4 14) My Project/Task.vb:6— Task's methods form 14 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: HCIsolatedTaskProxy (LCOM4 11) My Project/HCIsolatedTaskProxy.vb:10— HCIsolatedTaskProxy's methods form 11 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskPrint (LCOM4 7) My Project/TaskPrint.vb:3— TaskPrint's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: UtilsPreferences (LCOM4 6) My Project/UtilsPreferences.vb:5— UtilsPreferences's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskCheckMissingDrawing (LCOM4 6) My Project/TaskCheckMissingDrawing.vb:3— TaskCheckMissingDrawing's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskCheckInterference (LCOM4 5) My Project/TaskCheckInterference.vb:3— TaskCheckInterference's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskEditInteractively (LCOM4 5) My Project/TaskEditInteractively.vb:3— TaskEditInteractively's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskShowHideConstructions (LCOM4 5) My Project/TaskShowHideConstructions.vb:3— TaskShowHideConstructions's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskRunExternalProgram (LCOM4 5) My Project/TaskRunExternalProgram.vb:10— TaskRunExternalProgram's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskUpdatePartCopies (LCOM4 5) My Project/TaskUpdatePartCopies.vb:3— TaskUpdatePartCopies's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskCheckFilename (LCOM4 4) My Project/TaskCheckFilename.vb:3— TaskCheckFilename's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskSetDocumentStatus (LCOM4 4) My Project/TaskSetDocumentStatus.vb:3— TaskSetDocumentStatus's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskUpdateBlocks (LCOM4 4) My Project/TaskUpdateBlocks.vb:3— TaskUpdateBlocks's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskBreakLinks (LCOM4 4) My Project/TaskBreakLinks.vb:3— TaskBreakLinks's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskCheckDrawings (LCOM4 4) My Project/TaskCheckDrawings.vb:3— TaskCheckDrawings's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskCheckMaterialNotInMaterialTable (LCOM4 4) My Project/TaskCheckMaterialNotInMaterialTable.vb:3— TaskCheckMaterialNotInMaterialTable's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskCheckRelationships (LCOM4 4) My Project/TaskCheckRelationships.vb:3— TaskCheckRelationships's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskEditProperties (LCOM4 4) My Project/TaskEditProperties.vb:6— TaskEditProperties's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskEditVariables (LCOM4 4) My Project/TaskEditVariables.vb:5— TaskEditVariables's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskFitView (LCOM4 4) My Project/TaskFitView.vb:3— TaskFitView's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskCreateDrawingOfFlatPattern (LCOM4 4) My Project/TaskCreateDrawingOfFlatPattern.vb:5— TaskCreateDrawingOfFlatPattern's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskUpdateDrawingStylesFromTemplate (LCOM4 4) My Project/TaskUpdateDrawingStylesFromTemplate.vb:3— TaskUpdateDrawingStylesFromTemplate's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskUpdateDrawingViews (LCOM4 4) My Project/TaskUpdateDrawingViews.vb:3— TaskUpdateDrawingViews's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TaskUpdateMaterialFromMaterialTable (LCOM4 4) My Project/TaskUpdateMaterialFromMaterialTable.vb:3— TaskUpdateMaterialFromMaterialTable's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Change coupling: Form_Main.vb ↔ UtilsPreferences.vb My Project/Form_Main.vb— `My Project/Form_Main.vb` and `My Project/UtilsPreferences.vb` change together 68% of the time (69 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: TaskSaveDrawingAs.vb ↔ TaskSaveModelAs.vb My Project/TaskSaveDrawingAs.vb— `My Project/TaskSaveDrawingAs.vb` and `My Project/TaskSaveModelAs.vb` change together 67% of the time (42 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: FormPropertyPicker.vb ↔ Form_Main.vb My Project/FormPropertyPicker.vb— `My Project/FormPropertyPicker.vb` and `My Project/Form_Main.vb` change together 67% of the time (10 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: FormExpressionEditor.vb ↔ UtilsPowerShell.vb My Project/FormExpressionEditor.vb— `My Project/FormExpressionEditor.vb` and `My Project/UtilsPowerShell.vb` change together 65% of the time (13 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: Form_Main.vb ↔ TaskSetDocumentStatus.vb My Project/Form_Main.vb— `My Project/Form_Main.vb` and `My Project/TaskSetDocumentStatus.vb` change together 64% of the time (14 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: Form_Main.vb ↔ UCPropertyFilter.vb My Project/Form_Main.vb— `My Project/Form_Main.vb` and `My Project/UCPropertyFilter.vb` change together 62% of the time (10 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: UCEditProperties.vb ↔ UCPropertyFilter.vb My Project/UCEditProperties.vb— `My Project/UCEditProperties.vb` and `My Project/UCPropertyFilter.vb` change together 62% of the time (10 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: Form_Main.vb ↔ UtilsFileList.vb My Project/Form_Main.vb— `My Project/Form_Main.vb` and `My Project/UtilsFileList.vb` change together 58% of the time (86 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: Form_Main.vb ↔ UCEditProperties.vb My Project/Form_Main.vb— `My Project/Form_Main.vb` and `My Project/UCEditProperties.vb` change together 57% of the time (13 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: Form_Main.vb ↔ UtilsCommon.vb My Project/Form_Main.vb— `My Project/Form_Main.vb` and `My Project/UtilsCommon.vb` change together 56% of the time (67 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Duplicated block (15 lines × 2) My Project/HCPropertiesData.vb:1010— My Project/HCPropertiesData.vb:1010-1024 | My Project/HCPropertiesData.vb:1029-1043
Duplicated block (15 lines × 2) My Project/TaskUpdateBlocks.vb:1123— My Project/TaskUpdateBlocks.vb:1123-1137 | My Project/TaskUpdateBlocks.vb:1283-1297
Duplicated block (15 lines × 2) My Project/FormPropertyFilter.vb:350— My Project/FormPropertyFilter.vb:350-364 | My Project/FormPropertyInputEditor.vb:229-243
Duplicated block (15 lines × 2) My Project/UtilsPowerShell.vb:316— My Project/UtilsPowerShell.vb:316-327 | My Project/UtilsPowerShell.vb:384-398
Duplicated block (15 lines × 2) My Project/TaskEditProperties.vb:767— My Project/TaskEditProperties.vb:767-781 | My Project/TaskEditVariables.vb:307-321
Duplicated block (15 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:515— My Project/TaskCreateDrawingOfFlatPattern.vb:515-529 | My Project/TaskUpdateMaterialFromMaterialTable.vb:351-365
Duplicated block (15 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:834— My Project/TaskCreateDrawingOfFlatPattern.vb:834-848 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:905-919
Duplicated block (15 lines × 2) My Project/TaskSaveDrawingAs.vb:615— My Project/TaskSaveDrawingAs.vb:615-629 | My Project/TaskSaveModelAs.vb:915-929
Duplicated block (15 lines × 2) My Project/TaskSaveDrawingAs.vb:873— My Project/TaskSaveDrawingAs.vb:873-887 | My Project/TaskSaveModelAs.vb:1157-1171
Duplicated block (15 lines × 2) My Project/TaskUpdateMaterialFromMaterialTable.vb:397— My Project/TaskUpdateMaterialFromMaterialTable.vb:397-411 | My Project/TaskUpdateModelStylesFromTemplate.vb:1182-1194
Duplicated block (13 lines × 2) My Project/HCPropertiesData.vb:782— My Project/HCPropertiesData.vb:782-794 | My Project/HCPropertiesData.vb:797-809
Duplicated block (13 lines × 2) My Project/UtilsFileList.vb:1014— My Project/UtilsFileList.vb:1014-1026 | My Project/UtilsFileList.vb:1030-1042
Duplicated block (13 lines × 2) My Project/FormPropertyFilter.vb:534— My Project/FormPropertyFilter.vb:534-546 | My Project/FormVariableInputEditor.vb:358-370
Duplicated block (13 lines × 2) My Project/TaskCheckDrawings.vb:513— My Project/TaskCheckDrawings.vb:513-525 | My Project/TaskUpdateDrawingViews.vb:282-294
Duplicated block (13 lines × 2) My Project/TaskCheckDrawings.vb:606— My Project/TaskCheckDrawings.vb:606-618 | My Project/TaskUpdateDrawingViews.vb:332-344
Duplicated block (13 lines × 2) My Project/TaskSaveDrawingAs.vb:649— My Project/TaskSaveDrawingAs.vb:649-661 | My Project/TaskSaveModelAs.vb:940-952
Duplicated block (13 lines × 2) My Project/TaskSaveDrawingAs.vb:692— My Project/TaskSaveDrawingAs.vb:692-704 | My Project/TaskSaveModelAs.vb:983-995
Duplicated block (10 lines × 2) My Project/FormPropertyInputEditor.vb:329— My Project/FormPropertyInputEditor.vb:329-337 | My Project/UCTaskControl.vb:285-294
Duplicated block (10 lines × 2) My Project/TaskCheckInterference.vb:153— My Project/TaskCheckInterference.vb:153-162 | My Project/TaskCreateDrawingOfFlatPattern.vb:549-558
Duplicated block (10 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:581— My Project/TaskCreateDrawingOfFlatPattern.vb:581-590 | My Project/TaskCreateDrawingOfFlatPattern.vb:597-606
Duplicated block (10 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:748— My Project/TaskCreateDrawingOfFlatPattern.vb:748-757 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:931-940
Duplicated block (10 lines × 2) My Project/TaskPrint.vb:417— My Project/TaskPrint.vb:417-426 | My Project/TaskSaveDrawingAs.vb:687-696
Duplicated block (10 lines × 2) My Project/TaskUpdateMaterialFromMaterialTable.vb:421— My Project/TaskUpdateMaterialFromMaterialTable.vb:421-430 | My Project/TaskUpdateMaterialFromMaterialTable.vb:443-452
Duplicated block (10 lines × 2) My Project/UCTaskControl.vb:191— My Project/UCTaskControl.vb:191-200 | My Project/UCTaskControl.vb:218-227
Duplicated block (14 lines × 2) My Project/FormEditTaskList.vb:184— My Project/FormEditTaskList.vb:184-196 | My Project/FormPropertyListCustomize.vb:174-187
Duplicated block (14 lines × 2) My Project/FormEditTaskList.vb:325— My Project/FormEditTaskList.vb:325-338 | My Project/FormPropertyListCustomize.vb:311-324
Duplicated block (14 lines × 2) My Project/FormPropertyInputEditor.vb:409— My Project/FormPropertyInputEditor.vb:409-420 | My Project/FormVariableInputEditor.vb:290-303
Duplicated block (14 lines × 2) My Project/FormPropertyListCustomize.vb:344— My Project/FormPropertyListCustomize.vb:344-357 | My Project/FormPropertyListCustomize.vb:381-394
Duplicated block (14 lines × 2) My Project/TaskUpdateModelStylesFromTemplate.vb:965— My Project/TaskUpdateModelStylesFromTemplate.vb:965-978 | My Project/TaskUpdateModelStylesFromTemplate.vb:986-999
Duplicated block (11 lines × 2) My Project/Task.vb:280— My Project/Task.vb:280-290 | My Project/Task.vb:305-315
Duplicated block (11 lines × 2) My Project/TaskEditInteractively.vb:179— My Project/TaskEditInteractively.vb:179-189 | My Project/TaskRunExternalProgram.vb:110-120
Duplicated block (11 lines × 2) My Project/TaskSaveDrawingAs.vb:927— My Project/TaskSaveDrawingAs.vb:927-936 | My Project/TaskSaveModelAs.vb:1209-1219
Duplicated block (11 lines × 2) My Project/TaskSaveModelAs.vb:954— My Project/TaskSaveModelAs.vb:954-964 | My Project/TaskSaveModelAs.vb:997-1007
Duplicated block (11 lines × 2) My Project/UtilsTopLevelAssembly.vb:207— My Project/UtilsTopLevelAssembly.vb:207-217 | My Project/UtilsTopLevelAssembly.vb:222-231
Duplicated block (11 lines × 3) My Project/TaskUpdateBlocks.vb:402— My Project/TaskUpdateBlocks.vb:402-412 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:126-136 | My Project/TaskUpdateDrawingViews.vb:82-92
Duplicated block (11 lines × 3) My Project/TaskCheckDrawings.vb:123— My Project/TaskCheckDrawings.vb:123-133 | My Project/TaskPrint.vb:162-172 | My Project/TaskSaveDrawingAs.vb:219-229
Duplicated block (11 lines × 3) My Project/TaskCheckMissingDrawing.vb:41— My Project/TaskCheckMissingDrawing.vb:41-51 | My Project/TaskCheckRelationships.vb:67-77 | My Project/TaskSaveModelAs.vb:243-253
Duplicated block (11 lines × 3) My Project/TaskCheckPartCopies.vb:8— My Project/TaskCheckPartCopies.vb:8-18 | My Project/TaskUpdateFlatPattern.vb:8-18 | My Project/TaskUpdateDesignForCost.vb:8-18
Duplicated block (7 lines × 2) My Project/Form_Main.vb:2098— My Project/Form_Main.vb:2098-2104 | My Project/Form_Main.vb:2109-2115
Duplicated block (7 lines × 2) My Project/TaskFitView.vb:249— My Project/TaskFitView.vb:249-255 | My Project/TaskSaveModelAs.vb:1186-1192
Duplicated block (7 lines × 2) My Project/TaskPrint.vb:307— My Project/TaskPrint.vb:307-312 | My Project/UtilsCommon.vb:453-459
Duplicated block (7 lines × 2) My Project/TaskUpdateMaterialFromMaterialTable.vb:586— My Project/TaskUpdateMaterialFromMaterialTable.vb:586-592 | My Project/TaskUpdateMaterialFromMaterialTable.vb:601-607
XxxComment My Project/UtilsPreferences.vb:375— 'Outlist.Add("\\ System.Subject <-- need to end with this format L=xxx YY") — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment My Project/UtilsPreferences.vb:376— 'Outlist.Add("\\ xxx can be any number from 0 to 9999 And YY any two letters") — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment My Project/UtilsPreferences.vb:377— 'Outlist.Add("\\ xxx will be transformed in D4 syntax (example 65 will became 0065)") — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (16 lines × 2) My Project/FormPropertyInputEditor.vb:526— My Project/FormPropertyInputEditor.vb:526-541 | My Project/FormVariableInputEditor.vb:368-383
Duplicated block (16 lines × 2) My Project/UCPropertyFilter.vb:225— My Project/UCPropertyFilter.vb:225-240 | My Project/UCEditProperties.vb:236-251
Duplicated block (16 lines × 2) My Project/TaskUpdateModelStylesFromTemplate.vb:380— My Project/TaskUpdateModelStylesFromTemplate.vb:380-395 | My Project/TaskUpdateModelStylesFromTemplate.vb:420-435
Duplicated block (13 lines × 3) My Project/HCPropertiesData.vb:1059— My Project/HCPropertiesData.vb:1059-1071 | My Project/HCPropertiesData.vb:1074-1086 | My Project/HCPropertiesData.vb:1089-1101
Duplicated block (13 lines × 3) My Project/TaskSetDocumentStatus.vb:160— My Project/TaskSetDocumentStatus.vb:160-171 | My Project/TaskSaveDrawingAs.vb:790-802 | My Project/TaskUpdateModelSizeInVariableTable.vb:451-463
Duplicated block (13 lines × 3) My Project/FormEditTaskList.vb:361— My Project/FormEditTaskList.vb:361-373 | My Project/FormPropertyListCustomize.vb:346-358 | My Project/FormPropertyListCustomize.vb:383-395
Duplicated block (10 lines × 3) My Project/TaskEditProperties.vb:816— My Project/TaskEditProperties.vb:816-825 | My Project/TaskCreateDrawingOfFlatPattern.vb:629-638 | My Project/TaskCreateDrawingOfFlatPattern.vb:663-671
Duplicated block (10 lines × 3) My Project/TaskSaveDrawingAs.vb:742— My Project/TaskSaveDrawingAs.vb:742-751 | My Project/TaskSaveDrawingAs.vb:760-769 | My Project/TaskSaveDrawingAs.vb:778-787
Duplicated block (10 lines × 3) My Project/TaskSaveModelAs.vb:1035— My Project/TaskSaveModelAs.vb:1035-1044 | My Project/TaskSaveModelAs.vb:1045-1054 | My Project/TaskSaveModelAs.vb:1055-1064
TodoComment My Project/HCStructuredStorageDoc.vb:1228— ' ###### TODO: Maybe don't assume string, but check the actual property type and proceed accordingly. ###### — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment My Project/TaskUpdateBlocks.vb:1045— ' ###### TODO: Check for a duplicate block ###### — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (22 lines × 2) My Project/TaskEditProperties.vb:1087— My Project/TaskEditProperties.vb:1087-1106 | My Project/TaskRunExternalProgram.vb:640-661
Duplicated block (22 lines × 2) My Project/TaskUpdateModelStylesFromTemplate.vb:339— My Project/TaskUpdateModelStylesFromTemplate.vb:339-360 | My Project/TaskUpdateModelStylesFromTemplate.vb:384-400
Duplicated block (12 lines × 3) My Project/TaskCheckLinks.vb:669— My Project/TaskCheckLinks.vb:669-680 | My Project/TaskCheckMaterialNotInMaterialTable.vb:307-318 | My Project/TaskCheckMissingDrawing.vb:168-179
Duplicated block (12 lines × 3) My Project/TaskUpdateModelStylesFromTemplate.vb:1281— My Project/TaskUpdateModelStylesFromTemplate.vb:1281-1292 | My Project/TaskUpdateModelStylesFromTemplate.vb:1301-1312 | My Project/TaskUpdateModelStylesFromTemplate.vb:1321-1332
Duplicated block (8 lines × 2) My Project/TaskCheckLinks.vb:497— My Project/TaskCheckLinks.vb:497-504 | My Project/TaskCheckLinks.vb:521-528
Duplicated block (8 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:535— My Project/TaskCreateDrawingOfFlatPattern.vb:535-542 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:799-806
Duplicated block (34 lines × 3) My Project/TaskCheckMaterialNotInMaterialTable.vb:298— My Project/TaskCheckMaterialNotInMaterialTable.vb:298-307 | My Project/TaskEditProperties.vb:980-989 | My Project/TaskUpdateMaterialFromMaterialTable.vb:536-569
Duplicated block (24 lines × 2) My Project/HCStructuredStorageDoc.vb:1110— My Project/HCStructuredStorageDoc.vb:1110-1133 | My Project/HCStructuredStorageDoc.vb:1134-1157
Duplicated block (19 lines × 3) My Project/TaskCheckMaterialNotInMaterialTable.vb:266— My Project/TaskCheckMaterialNotInMaterialTable.vb:266-281 | My Project/TaskEditProperties.vb:914-928 | My Project/TaskUpdateMaterialFromMaterialTable.vb:646-664
Duplicated block (19 lines × 2) My Project/TaskCheckMaterialNotInMaterialTable.vb:210— My Project/TaskCheckMaterialNotInMaterialTable.vb:210-220 | My Project/TaskUpdateMaterialFromMaterialTable.vb:375-393
Duplicated block (17 lines × 5) My Project/TaskShowHideConstructions.vb:530— My Project/TaskShowHideConstructions.vb:530-544 | My Project/TaskShowHideConstructions.vb:563-577 | My Project/TaskShowHideConstructions.vb:596-610 | My Project/TaskShowHideConstructions.vb:630-646 | My Project/TaskShowHideConstructions.vb:715-729
Duplicated block (14 lines × 6) My Project/HCPropertiesData.vb:976— My Project/HCPropertiesData.vb:976-988 | My Project/HCPropertiesData.vb:991-1003 | My Project/HCPropertiesData.vb:1044-1056 | My Project/HCPropertiesData.vb:1104-1117 | My Project/HCPropertiesData.vb:1120-1132 | My Project/HCPropertiesData.vb:1135-1147
Duplicated block (13 lines × 5) My Project/TaskUpdateBlocks.vb:1222— My Project/TaskUpdateBlocks.vb:1222-1231 | My Project/TaskUpdateBlocks.vb:1232-1241 | My Project/TaskUpdateBlocks.vb:1242-1252 | My Project/TaskUpdateBlocks.vb:1273-1282 | My Project/TaskUpdateBlocks.vb:1283-1295
Duplicated block (13 lines × 4) My Project/TaskCheckFilename.vb:554— My Project/TaskCheckFilename.vb:554-566 | My Project/TaskUpdateBlocks.vb:1102-1114 | My Project/TaskCheckMaterialNotInMaterialTable.vb:216-228 | My Project/TaskEditProperties.vb:795-807
Duplicated block (12 lines × 5) My Project/TaskUpdateBlocks.vb:1308— My Project/TaskUpdateBlocks.vb:1308-1319 | My Project/TaskEditInteractively.vb:504-515 | My Project/TaskCreateDrawingOfFlatPattern.vb:683-694 | My Project/TaskRunExternalProgram.vb:449-460 | My Project/TaskSaveModelAs.vb:1087-1098
Duplicated block (12 lines × 2) My Project/TaskCheckFlatPattern.vb:60— My Project/TaskCheckFlatPattern.vb:60-71 | My Project/TaskUpdateFlatPattern.vb:59-70
Duplicated block (11 lines × 7) My Project/TaskCheckMaterialNotInMaterialTable.vb:70— My Project/TaskCheckMaterialNotInMaterialTable.vb:70-80 | My Project/TaskEditVariables.vb:56-66 | My Project/TaskShowHideConstructions.vb:388-398 | My Project/TaskUpdateModelSizeInVariableTable.vb:143-153 | My Project/TaskUpdateModelStylesFromTemplate.vb:210-220 | My Project/TaskUpdatePartCopies.vb:40-50 | My Project/TaskUpdatePhysicalProperties.vb:53-63
Duplicated block (11 lines × 6) My Project/TaskCheckFilename.vb:111— My Project/TaskCheckFilename.vb:111-121 | My Project/TaskSetDocumentStatus.vb:54-64 | My Project/TaskBreakLinks.vb:123-133 | My Project/TaskCheckLinks.vb:103-113 | My Project/TaskEditProperties.vb:114-124 | My Project/TaskFitView.vb:68-78
Duplicated block (11 lines × 4) My Project/TaskCheckFilename.vb:632— My Project/TaskCheckFilename.vb:632-642 | My Project/TaskCheckLinks.vb:670-680 | My Project/TaskCheckMaterialNotInMaterialTable.vb:308-318 | My Project/TaskCheckMissingDrawing.vb:169-179
Duplicated block (10 lines × 6) My Project/TaskUpdateBlocks.vb:1191— My Project/TaskUpdateBlocks.vb:1191-1200 | My Project/TaskEditInteractively.vb:413-422 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:823-832 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:833-842 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:843-852 | My Project/TaskUpdateMaterialFromMaterialTable.vb:467-476
Duplicated block (9 lines × 5) My Project/TaskEditInteractively.vb:397— My Project/TaskEditInteractively.vb:397-405 | My Project/TaskEditInteractively.vb:446-454 | My Project/TaskEditInteractively.vb:462-470 | My Project/TaskEditInteractively.vb:478-486 | My Project/TaskEditInteractively.vb:494-502
Duplicated block (9 lines × 3) My Project/TaskSetDocumentStatus.vb:150— My Project/TaskSetDocumentStatus.vb:150-158 | My Project/TaskUpdateBlocks.vb:1101-1109 | My Project/TaskCheckMaterialNotInMaterialTable.vb:215-223
Duplicated block (9 lines × 2) My Project/FormPropertyInputEditor.vb:177— My Project/FormPropertyInputEditor.vb:177-185 | My Project/FormVariableInputEditor.vb:105-113
Duplicated block (5 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:463— My Project/TaskCreateDrawingOfFlatPattern.vb:463-467 | My Project/TaskCreateDrawingOfFlatPattern.vb:469-473
Shell project: Housekeeper Housekeeper.vbproj— `Housekeeper` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: HousekeeperCLI HousekeeperCLI/HousekeeperCLI.vbproj— `HousekeeperCLI` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — No test projects found, so reliability couldn't be assessed.
D19 · Documentation Quality· No installation/run commands and no usage description exist in the visible text. · ×1
No installation/run commands and no usage description exist in the visible text. README.md— Add INSTALL/USAGE sections describing how to set up the project, run tests, and invoke the main API.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `Housekeeper` (36311 LoC, 131 public types across 1 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Rotate the exposed credentials — git history can't be un-committed — Some of these secrets are in git HISTORY: deleting the file does not remove them (the commit persists on every clone, fork and backup). The remediation is to ROTATE each historically-exposed credential and treat it as compromised — not to delete the file. Rewriting history is disruptive and unreliable across existing forks. (Working-tree-only secrets — no commit — can instead be removed from the file and moved to a secret store.)
D18 · Solution Shape· Build did not complete in the analyzer · ×1
Build did not complete in the analyzer — `dotnet build` reported 2 error(s) but no C# compiler diagnostic — an SDK / target-framework / restore mismatch in the analyzer environment, not a code defect (common for an older codebase whose target framework the analyzer's SDK can't build). Solution Shape is scored on structure and is NOT capped; the C# semantic analysis loads independently and is unaffected.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
trivy: not applicable — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
provenance: not applicable — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
osv-scanner: not applicable — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
0
—
Run 019fdec4-95d2-7bef-abc7-33cf5ec7f229 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 73 · Warnings: 392 · Recommendations: 7 · Info: 4 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 08-08-2026 @ 00:27 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.