Executive summary
IngmarStein/havm falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 67.0 out of 100 and is rated Adequate, and all six of its critical findings are security problems in the build pipeline and in its automatic dependency updates.
Production Readiness, at 61.9, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4.6 points. Adding automated security scanning would lift Production Readiness itself, worth about 3.1 points. Raising Production Readiness to 70 would lift the score to about 69.3.
Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version and setting a waiting period for automatic updates would close both risks.
The product code is 6,554 lines, about €11,000 to rebuild.
If Production Readiness rose from 61.9 to 70, the lowest score rated Strong, the score would rise from 67.0 to about 69.3.
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,600 to €18,000, for 59 to 188 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.9 at a score of 67. 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,554 lines of product code |
| 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 HavmCore | 2 docs.assets.js | 3 repository | 4 Havm |
|---|---|---|---|---|
| 1 HavmCore | ||||
| 2 docs.assets.js | ||||
| 3 repository | ||||
| 4 Havm | 5 |
4→1 Havm uses HavmCore✕
- Connections
- 5 pairs of types, where a type in Havm uses a type in HavmCore.
- The types involved
Havm.HavmApplicationDelegate→HavmCore.GuestStatusHavm.HavmApplicationDelegate→HavmCore.ServiceRuntimeHavm.ImportUTMCommand→HavmCore.UTMBundleHavm.RunCommand→HavmCore.LogFormatHavm.RunCommand→HavmCore.LogLevel
- Direction
- Havm uses HavmCore, so a change to HavmCore can break Havm, while a change to Havm can't break HavmCore.
- Position
- Below the diagonal: Havm 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 | 6 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift; 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; Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — 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 1 No ADRs found finding(s) in ADR Quality — start with Package.swift. | +4.6 pts | Low | ADR Quality |
| 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. | +3.6 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +3.1 pts | Medium | Security & performance tooling |
| Interpolated log message defeats structured logging | +2.3 pts | Medium | Structured logging |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.2 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.2 pts | Medium | Release Hygiene |
| Resolve the 3 No assertions finding(s) in Test Quality — start with UTMImportTests.swift (3). | +1.0 pts | Low | Test Quality |
| 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. | +1.3 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| Sources/HavmCore/ServiceRuntime.swift | 7.1 | Mixed | Cyclomatic Complexity: ServiceRuntime.performGracefulShutdown (cyclomatic 16) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| Tests/HavmCoreTests/UTMImportTests.swift | 7.4 | Mixed | Test Quality: No assertions: rejectsDrivePathTraversal |
| Sources/HavmCore/HAOSSetup.swift | 7.8 | Mixed | Cyclomatic Complexity: HAOSSetupManager.patchConsoleCmdline (cyclomatic 39) |
| Sources/HavmCore/UTMImport.swift | 7.8 | Mixed | Cyclomatic Complexity: UTMBundle.init (cyclomatic 27) |
| Sources/Havm/Commands/RunCommand.swift | 7.8 | Mixed | Cyclomatic Complexity: RunCommand.runService (cyclomatic 26) |
| Sources/Havm/Commands/ImportUTMCommand.swift | 7.8 | Mixed | Cyclomatic Complexity: ImportUTMCommand.run (cyclomatic 25) |
| Sources/HavmCore/VMController.swift | 7.8 | Mixed | Cyclomatic Complexity: VMController.createConfiguration (cyclomatic 16) |
| Sources/HavmCore/ConfigDiskBuilder.swift | 8.5 | Near-clean | Cognitive Complexity: ConfigDiskBuilder.build (cognitive 19) |
| Sources/Havm/Commands/CleanupCommand.swift | 8.5 | Near-clean | Cognitive Complexity: CleanupCommand.run (cognitive 16) |
| Package.swift | 9.5 | Near-clean | ADR Quality: No ADRs found |
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 41 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 — 41 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, 78 of 86 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
- D8 Code Coverage — 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. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — 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. Test source is present (.swift) and this repository declares a SwiftPM test suite (havm), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — 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. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 309 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D22 Internal API 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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. `Sources/Havm/Commands/ImportUTMCommand.swift`, `Sources/Havm/main.swift`, `Sources/HavmCore/HAOSSetup.swift`, `Sources/HavmCore/InstanceLock.swift`, `Sources/HavmCore/JSONLogHandler.swift`, … (+2 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.
- C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- GD1 Unfinished & placeholder code — 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 check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — 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 check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X12 Unreachable branch — 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 check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X15 Unvalidated length from an untrusted reader — 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 check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust, Dart, F# and Elixir source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust, Dart, F# or Elixir was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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 check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — 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 check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — 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 check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — 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 check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala, Kotlin, PHP and Go source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala, Kotlin, PHP or Go was found, and this repository's C is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — 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. 52 further occurrence(s) are not listed individually; the score already reflects all 92.
- X5 Nullable reference types — 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 check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's C, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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".
- 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
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HAOSSetupManager.patchConsoleCmdline at 39.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with HAOSSetupManager.patchConsoleCmdline (cyclomatic 39). — Refactoring it lifts Cyclomatic Complexity from 8.5 to about 8.8/10.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was HAOSSetupManager.patchConsoleCmdline at 57.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cognitive Complexity — start with HAOSSetupManager.patchConsoleCmdline (cognitive 57), UTMBundle.init (cognitive 39), ImportUTMCommand.run (cognitive 34). — 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 7 together lifts Cognitive Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with ServiceRuntime.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with ServiceRuntime.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with ServiceRuntime.swift. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
1 duplicated block group(s) detected. 0.2 % of the production lines (10 of 6,554) are in a reported copy.
What to do
- Resolve the 1 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ServiceRuntime.swift. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
3 production modules (SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 12 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 153 tests.
What to do
- Resolve the 3 No assertions finding(s) in Test Quality — start with UTMImportTests.swift (3). — One of this dimension's main actionable groups (3 warning-level).
D12 · Dependency Hygiene
2 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 38 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 38 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Swift Package.swift/Package.resolved, 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: Sources/HavmCore/HAOSSetup.swift (10×39=390); Sources/HavmCore/ServiceRuntime.swift (18×16=288); Sources/HavmCore/VMController.swift (11×16=176) Repeated repair below the complexity floor: Sources/HavmCore/USBAccessorySupport.swift (4 of 5 changes were fixes)
What to do
- Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with HAOSSetup.swift, ServiceRuntime.swift, VMController.swift. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with USBAccessorySupport.swift. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 6554 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 2 build units (Bundler, SwiftPM) flagged as possibly oversized/incoherent.
D27 · Navigability
7 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. 5 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 2 file(s) — `scripts/build.sh` (line 43), `scripts/publish.sh` (line 20) — 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 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 5 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 (5 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 21 of the 28 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
1/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 — start with REDACTED. — 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 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- 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.
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
- CONTRIBUTING.md links to `CLAUDE.md`, but `CLAUDE.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:72
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `CLAUDE.md`, but `CLAUDE.md` does not exist.
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (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 2 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
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `bundler`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `bundler` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — REDACTED:225
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X14 · Bypassable address classification
X3 · Exception handling
X4 · Structured logging
- `debug` at line 40 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.debug("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/ConfigWatcher.swift:40
- `warning` at line 243 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:243
- `info` at line 258 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:258
- `info` at line 267 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:267
- `warning` at line 274 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:274
- `info` at line 277 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:277
- `info` at line 280 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:280
- `info` at line 293 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:293
- `info` at line 311 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:311
- `warning` at line 315 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:315
- `warning` at line 332 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:332
- `info` at line 336 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:336
- `warning` at line 386 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:386
- `warning` at line 503 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:503
- `warning` at line 508 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:508
- `info` at line 521 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:521
- `info` at line 574 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:574
- `warning` at line 602 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:602
- `info` at line 619 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:619
- `warning` at line 634 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:634
- `debug` at line 641 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.debug("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:641
- `warning` at line 682 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:682
- `warning` at line 685 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:685
- `debug` at line 769 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.debug("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:769
- `warning` at line 806 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:806
- `info` at line 855 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/HAOSSetup.swift:855
- `warning` at line 83 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/InstanceLock.swift:83
- `debug` at line 408 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.debug("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/Metrics.swift:408
- `warning` at line 410 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/Metrics.swift:410
- `info` at line 412 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/Metrics.swift:412
- `error` at line 414 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.error("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/Metrics.swift:414
- `debug` at line 416 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.debug("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/Metrics.swift:416
- `warning` at line 20 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/PIDFile.swift:20
- `debug` at line 28 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.debug("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/PIDFile.swift:28
- `info` at line 158 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/ServiceRuntime.swift:158
- `error` at line 177 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.error("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/ServiceRuntime.swift:177
- `info` at line 325 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/ServiceRuntime.swift:325
- `info` at line 468 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/ServiceRuntime.swift:468
- `info` at line 496 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.info("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/ServiceRuntime.swift:496
- `warning` at line 500 is handed a message with values interpolated or concatenated into it through swift-log, so the handler receives one finished `Logger.Message` — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as metadata instead: `logger.warning("order moved", metadata: ["order_id": "\(orderID)", "status": "\(status)"])`, which a structured LogHandler keeps as keys. — Sources/HavmCore/ServiceRuntime.swift:500
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71.1 | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96.6 | Exemplary | Solid. |
| Maturity | 63.0 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61.9 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 77.3 | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Not evidenced — 2 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no interface, protocol or abstract type declares an operation an implementer must write
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — 1 markup document under demonstration, documentation or developer-tool trees (or modules the build marks non-production) but none in the product; no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — those pages are demos or docs for the code, not something this tier can boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (892 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — 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"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .swift source were not judged.
- D25 ADR Conformance — no ADRs to check
- 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) — 7 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.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Swift suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- 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.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 1% of this repository's production lines — swift (6,554 lines), c (161 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — 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
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — 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 — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 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 — 6 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 29 finding(s)
- Hotspot: Sources/HavmCore/HAOSSetup.swift Sources/HavmCore/HAOSSetup.swift:695
- Hotspot: Sources/HavmCore/ServiceRuntime.swift Sources/HavmCore/ServiceRuntime.swift:596
- Hotspot: Sources/HavmCore/VMController.swift Sources/HavmCore/VMController.swift:54
- Hotspot: Sources/Havm/Commands/RunCommand.swift Sources/Havm/Commands/RunCommand.swift:98
- Hotspot: Sources/Havm/Commands/ImportUTMCommand.swift Sources/Havm/Commands/ImportUTMCommand.swift:43
- No assertions: rejectsDrivePathTraversal Tests/HavmCoreTests/UTMImportTests.swift:76
- No assertions: rejectsEFIPathTraversal Tests/HavmCoreTests/UTMImportTests.swift:92
- No assertions: rejectsAbsoluteDrivePath Tests/HavmCoreTests/UTMImportTests.swift:109
- HAOSSetupManager.patchConsoleCmdline (cyclomatic 39) Sources/HavmCore/HAOSSetup.swift:695
- UTMBundle.init (cyclomatic 27) Sources/HavmCore/UTMImport.swift:35
- RunCommand.runService (cyclomatic 26) Sources/Havm/Commands/RunCommand.swift:98
- ImportUTMCommand.run (cyclomatic 25) Sources/Havm/Commands/ImportUTMCommand.swift:43
- ServiceRuntime.performGracefulShutdown (cyclomatic 16) Sources/HavmCore/ServiceRuntime.swift:596
- VMController.createConfiguration (cyclomatic 16) Sources/HavmCore/VMController.swift:54
- Repeated repair: Sources/HavmCore/USBAccessorySupport.swift Sources/HavmCore/USBAccessorySupport.swift:179
- HAOSSetupManager.patchConsoleCmdline (cognitive 57) Sources/HavmCore/HAOSSetup.swift:695
- UTMBundle.init (cognitive 39) Sources/HavmCore/UTMImport.swift:35
- ImportUTMCommand.run (cognitive 34) Sources/Havm/Commands/ImportUTMCommand.swift:43
- RunCommand.runService (cognitive 27) Sources/Havm/Commands/RunCommand.swift:98
- VMController.createConfiguration (cognitive 26) Sources/HavmCore/VMController.swift:54
- ConfigDiskBuilder.build (cognitive 19) Sources/HavmCore/ConfigDiskBuilder.swift:15
- CleanupCommand.run (cognitive 16) Sources/Havm/Commands/CleanupCommand.swift:24
- ClassTooLong: ServiceRuntime Sources/HavmCore/ServiceRuntime.swift:52
- FileTooLong: HavmCore/ServiceRuntime.swift Sources/HavmCore/ServiceRuntime.swift
- TooManyMethods: ServiceRuntime Sources/HavmCore/ServiceRuntime.swift:52
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) Sources/HavmCore/ServiceRuntime.swift:568
Minor — 49 finding(s)
- Interpolated log message defeats structured logging Sources/HavmCore/ConfigWatcher.swift:40
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:243
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:258
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:267
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:274
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:277
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:280
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:293
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:311
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:315
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:332
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:336
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:386
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:503
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:508
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:521
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:574
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:602
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:619
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:634
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:641
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:682
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:685
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:769
- Interpolated log message defeats structured logging Sources/HavmCore/HAOSSetup.swift:806
- No ADRs found Package.swift:10
- REDACTED
- REDACTED
- No ADRs
- README/code drift CONTRIBUTING.md:72
- No SAST REDACTED:6
- Dependabot does not watch bundler REDACTED:2
- No release approval gate REDACTED:225
- No changelog
Minor — 2 finding(s)
- Outdated: swift-log
- Outdated: swift-metrics
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-3a051d4601e144a98af6725ddd30cb6e/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=110" --report-format json --report-path /tmp/watchdog-gitleaks-3a051d4601e144a98af6725ddd30cb6e/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.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-3a051d4601e144a98af6725ddd30cb6e/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 . | 6 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.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 7 file(s) — `Sources/Havm/Commands/ImportUTMCommand.swift`, `Sources/Havm/main.swift`, `Sources/HavmCore/HAOSSetup.swift`, `Sources/HavmCore/InstanceLock.swift`, `Sources/HavmCore/JSONLogHandler.swift`, … (+2 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |