Public report — Aetheris, published 29 Jul 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
397findings with an exact file:lineof 410 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
46/112dimensions across the health lenses68817 LoC — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
Colin4k1024/Aetheris is sound in substance but carries real gaps (56%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Domain Modelling (100%) — the domain model is expressive and well-guarded. Architecture (94%) is solid too.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Security (42%) — exposure to security and compliance incidents is elevated. Accessibility (59%) is the next concern — it raises ongoing delivery and operational cost.
Leadership focus, highest impact first: 37 High finding(s) (Static Analysis (SAST)); Declare <html lang>, a document <title> and a <main> landmark,… (Page structure); Keep a visible focus style (don't remove the outline without… (Visual & motion safety).
For scale: Medium (~68,817 production lines); rebuilding it from scratch would take roughly ~0.8 person-years (~1–2 engineers). Approximate, ±~30%.
It builds on a genuinely strong Domain Modelling foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
141 finding(s) are new versus the previous scan (2026-07-20) — surfaced by this scheduled scan itself, no pull request required. Showing the first 100; the full set is in the report.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.8× (at 56% quality) — the last 20% of quality is most of the work
Size & shape
Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.8 person-years of build effort (about ~€120,000 to rebuild). Its weakest lens is Security at 42% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — domain model × a 0.8× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 8 Secret finding(s) in Secrets (history) — start with events.json (2), trace.json (2), agent-ledger.json.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~0.8 person-years to rebuild), and its weakest lens is Security at 42%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Security first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Resolve the 37 High finding(s) in Static Analysis (SAST) — start with ci.yml (12), homepage-pages.yml (4), slsa-release.yml (4). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Resolve the 37 High finding(s) in Static Analysis (SAST) — start with ci.yml (12), homepage-pages.yml (4), slsa-release.yml (4).
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 5.5/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 6–14% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2 complexity, D4 duplication, D6 cohesion: averaging 5.5/10 across the code-quality signals
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
At a glance — Code Health · 70% · Adequate · gated by D2
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
46
High / Critical
A06:2021 — Vulnerable & Outdated Components
22
High / Critical
A02:2021 — Cryptographic Failures
9
High / Critical
A05:2021 — Security Misconfiguration
7
High / Critical
Roadmap
Begin by resolving the 37 high-priority static analysis findings in your CI workflows, specifically targeting ci.yml, homepage-pages.yml, and slsa-release.yml. Next, address the 35 structural accessibility checks by ensuring proper HTML landmarks, titles, and heading hierarchy. Simultaneously, improve visual safety by maintaining visible focus styles, respecting reduced motion preferences, and fixing low-contrast color pairs. Finally, implement an HTML-template accessibility linter and integrate automated testing to enforce these standards in your CI pipeline, while also clearing 8 secret findings from your repository history.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 8 Secret finding(s) in Secrets (history) — start with events.json (2), trace.json (2), agent-ledger.json.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Enforce accessibility in the toolchain: add an a11y linter that can read your UI — no component framework was detected, so the JSX/Vue ESLint plugins would have nothing to lint; use an HTML-template a11y linter (html-eslint, htmlhint) or run axe/pa11y over the rendered pages, assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 43 of 46 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.7 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 46 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 397 of 410 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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").
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A clean result is "no unlabelled native control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D20, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 54 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 api.NewApp (cyclomatic 195) finding(s) in Cyclomatic Complexity — start with app.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Runner.RunForJob (cyclomatic 191) finding(s) in Cyclomatic Complexity — start with runner.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 http.BuildNarrative (cyclomatic 103) finding(s) in Cyclomatic Complexity — start with trace_narrative.go. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 109 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 main.main (cognitive 44) finding(s) in Cognitive Complexity — start with main.go (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Runner.RunForJob (cognitive 585) finding(s) in Cognitive Complexity — start with runner.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 api.NewApp (cognitive 314) finding(s) in Cognitive Complexity — start with app.go. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.4 / 10Exemplary✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
Of 2 mechanizable ADRs, 0 are prevented by analyzers, 2 by tests, 0 exist only in prose. Coverage: 100 %. Cycles found: 0.
What to do
Enforce Architectural Integrity in CI to reach Prevented (currently Verified). — Hardens enforcement from Verified toward Prevented — provenance only; does not change the score.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.3 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
25 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is templates/autonomous-researcher/workflow.go.
Off-boarding risk: anonymized user #1 · ×3
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
A clear, well-structured README for an open-source runtime named Aetheris that solves AI-process-crash-and-retry problems. The document is backed by production proof (crash recovery demo, Grafana dashboard, k6 load test, Go benchmark) and a four-layer architecture outline, plus a dedicated Workflow Templates section with four ready-to-use agent types. Examples are present in the examples/ directory.
The 'Without Aetheris: retry → email sent twice' failure mode is mentioned but never verified by code or test.README.md
The 'Quick verification: ... make docker-run' section is ideal but the full command line and how to run benchmarks is cut off mid-sentence.README.md
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Secret: generic-api-key · ×8examples/customer_support_agent/artifacts/agent-ledger.json:63detected by gitleaks finding
Rotate the exposed credentials — git history can't be un-committed
What to do
Resolve the 8 Secret finding(s) in Secrets (history) — start with events.json (2), trace.json (2), agent-ledger.json. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
High: github-actions-mutable-action-tag · ×37.github/workflows/ci.yml:20detected by semgrep finding
Medium: insecure-hash-algorithm-sha1 · ×4examples/customer_support_agent/agent.py:274detected by semgrep finding
Low: dynamic-urllib-use-detected · ×5examples/customer_support_agent/demo.py:196detected by semgrep finding
What to do
Resolve the 37 High finding(s) in Static Analysis (SAST) — start with ci.yml (12), homepage-pages.yml (4), slsa-release.yml (4). — One of this dimension's main actionable groups (37 issue-level).
Resolve the 5 Low finding(s) in Static Analysis (SAST) — start with oidc.go (2), demo.py, app.go. — One of this dimension's main actionable groups (5 recommendation-level).
Resolve the 4 Medium finding(s) in Static Analysis (SAST) — start with agent.py, contract.go, app.go. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
High IaC: DS-0002 · ×4deployments/compose/Dockerfiledetected by trivy finding
Low IaC: DS-0026 · ×3deployments/compose/Dockerfiledetected by trivy finding
What to do
Resolve the 4 High IaC finding(s) in IaC & Container Security — start with Dockerfile (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with Dockerfile (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
64 of 254 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is pkg/routing/model.go.
Further orphaned files (smaller)
What to do
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PR-triggered workflow without a permissions block finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No SBOM finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
A vulnerability-disclosure policy (SECURITY.md) is present but lists no reporting contact.
Disclosure policy has no reporting contact
What to do
Resolve the 1 Disclosure policy has no reporting contact finding(s) in Vulnerability-disclosure Policy. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d37_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×7sdk/openclaw-adapter/package-lock.jsondetected by osv-scanner finding
Critical CVE: [GHSA redacted] · ×3go.moddetected by osv-scanner finding
High vulnerability: [GHSA redacted]sdk/openclaw-adapter/package-lock.jsondetected by osv-scanner finding
Medium CVE: GO-2026-4503 · ×8go.moddetected by osv-scanner finding
Low CVE: [GHSA redacted] · ×2sdk/openclaw-adapter/package-lock.jsondetected by osv-scanner finding
What to do
Resolve the 7 High CVE finding(s) in OSV Dependency Vulnerabilities — start with go.mod (4), package-lock.json (3). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 3 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with go.mod (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Do you agree with this assessment?
AC2 · Forms & labels6.0 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×4) — subscribe.html:168, index.html:545, index.html:556, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — index.html:2, subscribe.html:2, index.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
This stylesheet animates but never checks prefers-reduced-motion, so motion-sensitive users can't opt out. Wrap motion in @media (prefers-reduced-motion: no-preference). — index.html:7
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an a11y linter (eslint-plugin-jsx-a11y / vuejs-accessibility) configured, and axe/pa11y/Lighthouse wired into tests or CI — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an a11y linter (eslint-plugin-jsx-a11y / vuejs-accessibility) configured, and axe/pa11y/Lighthouse in tests or CI, graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
No accessibility enforcement found — no a11y linter (an a11y linter that can read your UI — no component framework was detected, so the JSX/Vue ESLint plugins would have nothing to lint; use an HTML-template a11y linter (html-eslint, htmlhint) or run axe/pa11y over the rendered pages) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time.
What to do
Enforce accessibility in the toolchain: add an a11y linter that can read your UI — no component framework was detected, so the JSX/Vue ESLint plugins would have nothing to lint; use an HTML-template a11y linter (html-eslint, htmlhint) or run axe/pa11y over the rendered pages, assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (TypeORM/Prisma/MikroORM/Sequelize/Mongoose) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a 'Testing' section to the root README — how to run the test suite.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
P5 · DR & Backup10.0 / 10Exemplary✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
What to do
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×2) — extension.ts:683, aetheris-client.ts:112
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files4.3 / 10Weak✓ Tool-verified
React / JS · Code Health — How many components/modules exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
1 file(s) over 400 lines
What to do
Split the oversized components into smaller, focused ones.
Do you agree with this assessment?
R4 · Test Coverage7.1 / 10Strong✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. If it is a CLI, check whether a suite runs it as a child process; otherwise it has no test reaching it. (×2) — extension.ts, index.ts
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D33 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D33). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.9 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Nothing imports this binding — it is safe to review for removal. — utils.ts:32
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in tools/vscode-extension/package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Not included — 66 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over the .NET document set and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over the .NET project-reference graph and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over the .NET project-reference graph and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from the .NET project graph (projects, types, namespaces) and no such graph was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over the .NET type surface and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — not assessed — test isolation is computed from the .NET project graph (which projects are test projects, and what they reference) and no such graph was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — no data
C1 Data Protection — Not assessed: these personal data controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom 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 C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom 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.
C3 Audit Trail — Not assessed: these audit controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom 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.
C4 Data Retention — Not assessed: these retention controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks retention 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.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks data-subject rights 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.
D10 Test Quality — ~35421 lines of test source are present (.go, .ts) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (a Go module (go.mod/go.sum)), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
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.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.go, .py, .ts) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["Acme.Billing"]`, `Catalog: ["Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — none of 3 ADRs are conformance-checkable — unverifiable.
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Go module (go.mod/go.sum) — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
D32 Data Compliance (PII/GDPR) — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is mostly .go, .py, .ts, which this pass does not read, so cohesion was not assessed for this repository. Not scored — this is a gap in the analyzer, not a finding about this repository.
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.go, .ts) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Aggregate boundaries — not scored for TypeScript: a class holding another class reads the same whether the inner type is an aggregate or a value object, so this cannot be decided from source without guessing — reported as guidance rather than measured
DM2 Strongly-typed ids — not scored for TypeScript: branded ids (`type Id = string & { __brand }`) are an uncommon idiom, so a bare-string id is not on its own evidence of a missing typed id — reported as guidance rather than measured
DM3 Integration-event coupling — not scored for TypeScript: a domain type used across packages is indistinguishable in source from a deliberate shared-kernel package, so this is reported as guidance rather than measured
DM4 Rich vs anemic model — not scored for TypeScript: telling a rich domain entity from an anemic data holder needs the behaviour a source-only read cannot always attribute (components, DTOs and readonly value objects are all legitimately data-shaped), so this is reported as guidance rather than measured
DM5 Encapsulated state — not scored for TypeScript: the language already steers state behind #private/private/readonly, so a mutable public field is rare enough that we report this as guidance rather than measuring it
DM7 Repository granularity — not scored for TypeScript: deciding whether a repository belongs to an aggregate root needs the aggregate structure, which source alone does not state — reported as guidance rather than measured
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 15 event-sourced shape(s) (event folds / event-recording aggregates); a store-then-publish dual write (persist + broker publish in one flow)
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): an append-only event-store seam (IEventStore/Append-of-events); 15 Go aggregate(s) recording domain events (own events-slice append / raise-record)
GD1 Unfinished & placeholder code — no source files
IC1 Incompleteness & stubs — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no data
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — not assessed — schema-migration practice is read from 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
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
S1 Web-Security Posture — Not assessed: these web-security controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom 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.
SC1 Supply-chain hygiene — no data
X1 Async correctness — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X3 Exception handling — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X4 Structured logging — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:20— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:23— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: reviewdog/action-actionlint@<40-character SHA>`. This step references `reviewdog/action-actionlint@v1`; resolve the SHA it points at today with `gh api repos/reviewdog/action-actionlint/commits/v1 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:32— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:35— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-go@<40-character SHA>`. This step references `actions/setup-go@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-go/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:84— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: codecov/codecov-action@<40-character SHA>`. This step references `codecov/codecov-action@v4`; resolve the SHA it points at today with `gh api repos/codecov/codecov-action/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:100— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:103— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-go@<40-character SHA>`. This step references `actions/setup-go@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-go/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:135— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:138— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-go@<40-character SHA>`. This step references `actions/setup-go@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-go/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:171— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:174— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-go@<40-character SHA>`. This step references `actions/setup-go@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-go/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:193— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/dependency-review.yml:19— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/dependency-review.yml:22— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-go@<40-character SHA>`. This step references `actions/setup-go@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-go/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/dependency-review.yml:40— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/homepage-pages.yml:28— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/homepage-pages.yml:31— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/configure-pages@<40-character SHA>`. This step references `actions/configure-pages@v5`; resolve the SHA it points at today with `gh api repos/actions/configure-pages/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/homepage-pages.yml:34— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-pages-artifact@<40-character SHA>`. This step references `actions/upload-pages-artifact@v3`; resolve the SHA it points at today with `gh api repos/actions/upload-pages-artifact/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/homepage-pages.yml:48— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/deploy-pages@<40-character SHA>`. This step references `actions/deploy-pages@v4`; resolve the SHA it points at today with `gh api repos/actions/deploy-pages/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/monthly-release.yml:26— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/monthly-release.yml:31— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-go@<40-character SHA>`. This step references `actions/setup-go@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-go/commits/v5 --jq .sha`.
High: run-shell-injection .github/workflows/monthly-release.yml:41— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/workflows/pr-serial-gate.yml:18— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/github-script@<40-character SHA>`. This step references `actions/github-script@v7`; resolve the SHA it points at today with `gh api repos/actions/github-script/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/slsa-release.yml:29— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/slsa-release.yml:35— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-go@<40-character SHA>`. This step references `actions/setup-go@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-go/commits/v5 --jq .sha`.
D38 · OSV Dependency Vulnerabilities· High CVE · ×7
High CVE: [GHSA redacted] sdk/openclaw-adapter/package-lock.json— brace-expansion 1.1.14: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 1.1.16 with an `overrides` entry). One upgrade of brace-expansion 1.1.14 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] sdk/openclaw-adapter/package-lock.json— form-data 4.0.5: [GHSA redacted] — form-data is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin form-data to 4.0.6 with an `overrides` entry).
High CVE: [GHSA redacted] go.mod— github.com/buger/jsonparser 1.1.1: [GHSA redacted] — github.com/buger/jsonparser is not a DIRECT requirement of this module: go.mod records it as `// indirect`, pulled in transitively, so raise it in place (run `go get github.com/buger/jsonparser@v1.1.2`, which updates the require line go.mod already holds for it).
High CVE: [GHSA redacted] go.mod— go.opentelemetry.io/otel 1.40.0: [GHSA redacted] — upgrade to 1.41.0
High CVE: [GHSA redacted] go.mod— go.opentelemetry.io/otel/sdk 1.40.0: [GHSA redacted] — upgrade to 1.43.0
High CVE: [GHSA redacted] go.mod— golang.org/x/image 0.24.0: [GHSA redacted] — golang.org/x/image is not a DIRECT requirement of this module: go.mod records it as `// indirect`, pulled in transitively, so raise it in place (run `go get golang.org/x/image@v0.41.0`, which updates the require line go.mod already holds for it). One upgrade of golang.org/x/image 0.24.0 clears all 8 advisories it raises: [GHSA redacted], [GHSA redacted], GO-2026-4961, GO-2026-4962, GO-2026-5031, GO-2026-5061, GO-2026-5062, GO-2026-5066.
High CVE: [GHSA redacted] sdk/openclaw-adapter/package-lock.json— js-yaml 3.14.2: [GHSA redacted] — js-yaml is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin js-yaml to 3.15.0 with an `overrides` entry). One upgrade of js-yaml 3.14.2 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
Boundary-crossing change coupling: client.go ↔ router.go cmd/cli/client.go— `cmd/cli/client.go` (context cmd) and `internal/api/http/router.go` (context internal) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched the less-changed of the two, renames followed) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
D38 · OSV Dependency Vulnerabilities· High vulnerability · ×1
High vulnerability: [GHSA redacted] sdk/openclaw-adapter/package-lock.json— axios 1.16.0: [GHSA redacted] — upgrade to 1.18.0 One upgrade of axios 1.16.0 clears all 10 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Duplicated block (10 lines × 2) internal/agent/runtime/executor/node_adapter.go:333— internal/agent/runtime/executor/node_adapter.go:333-342 | internal/agent/runtime/executor/node_adapter.go:345-354 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) internal/agent/runtime/executor/node_adapter.go:814— internal/agent/runtime/executor/node_adapter.go:814-823 | internal/agent/runtime/executor/node_adapter.go:831-840 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) internal/agent/runtime/executor/node_adapter.go:882— internal/agent/runtime/executor/node_adapter.go:882-891 | internal/agent/runtime/executor/node_adapter.go:899-908 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) internal/agent/runtime/executor/runner.go:773— internal/agent/runtime/executor/runner.go:773-782 | internal/agent/runtime/executor/runner.go:1262-1271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) internal/agent/runtime/session.go:232— internal/agent/runtime/session.go:232-241 | internal/runtime/session/session.go:190-199 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) internal/agent/runtime/state.go:67— internal/agent/runtime/state.go:67-76 | internal/agent/runtime/state.go:94-103 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) internal/agent/tools/registry.go:99— internal/agent/tools/registry.go:99-108 | internal/tool/registry/registry.go:74-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) internal/api/http/handler.go:1838— internal/api/http/handler.go:1838-1847 | internal/api/http/handler.go:1972-1981 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) internal/api/http/handler.go:1932— internal/api/http/handler.go:1932-1941 | internal/api/http/handler.go:2003-2012 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) internal/app/api/app.go:430— internal/app/api/app.go:430-439 | internal/app/worker/app.go:494-503 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) internal/app/api/app.go:469— internal/app/api/app.go:469-478 | internal/app/worker/app.go:281-290 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) internal/app/api/app.go:570— internal/app/api/app.go:570-579 | internal/app/worker/app.go:317-326 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) internal/tool/builtin/ingest.go:78— internal/tool/builtin/ingest.go:78-87 | internal/tool/builtin/rag_search.go:88-97 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) internal/einoext/factory.go:59— internal/einoext/factory.go:59-68 | internal/einoext/factory.go:110-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) internal/agent/executor/executor.go:47— internal/agent/executor/executor.go:47-57 | internal/agent/executor/executor.go:77-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) internal/agent/runtime/executor/eino_agent/agent.go:355— internal/agent/runtime/executor/eino_agent/agent.go:355-366 | internal/agent/runtime/executor/eino_examples/adapters.go:565-575 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (11 lines × 2) internal/agent/runtime/executor/eino_agent/agent.go:408— internal/agent/runtime/executor/eino_agent/agent.go:408-418 | internal/agent/runtime/executor/eino_examples/adapters.go:618-628 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (11 lines × 2) internal/agent/runtime/executor/runner.go:741— internal/agent/runtime/executor/runner.go:741-751 | internal/agent/runtime/executor/runner.go:782-792 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) internal/agent/runtime/executor/runner.go:931— internal/agent/runtime/executor/runner.go:931-941 | internal/agent/runtime/executor/runner.go:1531-1541 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) internal/api/http/handler.go:1348— internal/api/http/handler.go:1348-1358 | internal/api/http/handler.go:1392-1402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) internal/api/http/handler.go:1855— internal/api/http/handler.go:1855-1865 | internal/api/http/handler.go:2020-2030 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) internal/app/api/node_sink.go:201— internal/app/api/node_sink.go:201-211 | internal/app/api/node_sink.go:374-384 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) internal/app/worker/app.go:379— internal/app/worker/app.go:379-389 | internal/app/worker/app.go:536-546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) internal/model/llm/effect_adapter.go:58— internal/model/llm/effect_adapter.go:58-68 | internal/model/llm/effect_adapter.go:254-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) internal/model/llm/rate_limited_client.go:47— internal/model/llm/rate_limited_client.go:47-57 | internal/model/llm/rate_limited_client.go:83-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) pkg/agent/sdk/agent.go:48— pkg/agent/sdk/agent.go:48-58 | pkg/agent/sdk/agent.go:70-80 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) examples/ai-customer-bot/bot.go:268— examples/ai-customer-bot/bot.go:268-283 | examples/ai-customer-bot/bot.go:312-326 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) internal/agent/instance/store_pg.go:67— internal/agent/instance/store_pg.go:67-81 | internal/agent/instance/store_pg.go:166-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) internal/agent/runtime/executor/eino_agent/agent.go:372— internal/agent/runtime/executor/eino_agent/agent.go:372-386 | internal/agent/runtime/executor/eino_examples/adapters.go:585-599 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (15 lines × 2) internal/agent/runtime/executor/eino_agent/agent.go:534— internal/agent/runtime/executor/eino_agent/agent.go:534-548 | internal/agent/runtime/executor/eino_examples/adapters.go:1069-1083 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (15 lines × 2) internal/agent/runtime/executor/runner.go:908— internal/agent/runtime/executor/runner.go:908-922 | internal/agent/runtime/executor/runner.go:1504-1519 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) internal/agent/runtime/executor/state_diff.go:111— internal/agent/runtime/executor/state_diff.go:111-125 | internal/api/http/trace_narrative.go:585-599 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (15 lines × 2) internal/api/http/trace_narrative.go:131— internal/api/http/trace_narrative.go:131-145 | internal/api/http/trace_tree.go:58-72 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (15 lines × 2) internal/api/http/trace_tree.go:249— internal/api/http/trace_tree.go:249-263 | internal/api/http/trace_tree.go:282-296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) internal/app/api/app.go:607— internal/app/api/app.go:607-621 | internal/app/worker/app.go:364-378 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (15 lines × 2) internal/runtime/eino/engine.go:164— internal/runtime/eino/engine.go:164-178 | internal/runtime/eino/engine.go:195-209 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) internal/storage/vector/memory.go:242— internal/storage/vector/memory.go:242-256 | internal/storage/vector/pipeline/pipeline.go:473-487 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (17 lines × 2) internal/agent/job/pg_store.go:413— internal/agent/job/pg_store.go:413-429 | internal/agent/job/pg_store.go:454-470 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) internal/agent/replay/replay.go:254— internal/agent/replay/replay.go:254-270 | internal/agent/replay/replay.go:621-637 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) internal/agent/runtime/executor/eino_examples/adapters.go:763— internal/agent/runtime/executor/eino_examples/adapters.go:763-779 | internal/agent/runtime/executor/eino_examples/adapters.go:887-903 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) internal/agent/runtime/executor/eino_examples/llm.go:196— internal/agent/runtime/executor/eino_examples/llm.go:196-213 | internal/agent/runtime/executor/eino_examples/llm.go:288-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) internal/api/http/handler.go:706— internal/api/http/handler.go:706-722 | internal/app/api/adk_agent.go:80-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (17 lines × 2) internal/model/llm/claude.go:86— internal/model/llm/claude.go:86-102 | internal/model/llm/claude.go:147-163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) internal/runtime/eino/workflow.go:166— internal/runtime/eino/workflow.go:166-182 | internal/runtime/eino/workflow.go:203-219 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) pkg/compliance/residency.go:116— pkg/compliance/residency.go:116-132 | pkg/compliance/residency.go:147-163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) pkg/effects/tool.go:69— pkg/effects/tool.go:69-87 | pkg/effects/tool.go:110-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) pkg/routing/failover.go:112— pkg/routing/failover.go:112-129 | pkg/routing/failover.go:132-148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) internal/agent/messaging/store_mem.go:125— internal/agent/messaging/store_mem.go:125-136 | internal/agent/messaging/store_mem.go:147-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) internal/agent/runtime/executor/runner.go:1225— internal/agent/runtime/executor/runner.go:1225-1236 | internal/agent/runtime/executor/runner.go:1271-1282 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) internal/api/http/handler.go:2148— internal/api/http/handler.go:2148-2159 | internal/api/http/handler.go:2166-2177 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) internal/app/api/app.go:307— internal/app/api/app.go:307-318 | internal/app/worker/app.go:896-908 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (12 lines × 2) internal/app/api/app.go:939— internal/app/api/app.go:939-951 | internal/app/worker/app.go:827-838 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (12 lines × 2) internal/model/llm/effect_adapter.go:259— internal/model/llm/effect_adapter.go:259-270 | internal/model/llm/effect_adapter.go:291-302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) internal/pipeline/ingest/loader.go:145— internal/pipeline/ingest/loader.go:145-156 | internal/pipeline/ingest/loader.go:192-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) internal/tool/gatekeeper/gatekeeper.go:389— internal/tool/gatekeeper/gatekeeper.go:389-400 | internal/tool/gatekeeper/gatekeeper.go:412-423 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) pkg/config/config.go:861— pkg/config/config.go:861-872 | pkg/config/config.go:896-907 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) pkg/security/mtls/mtls.go:45— pkg/security/mtls/mtls.go:45-56 | pkg/security/mtls/mtls.go:84-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D38 · OSV Dependency Vulnerabilities· Medium CVE · ×8
Medium CVE: GO-2026-4503 go.mod— filippo.io/edwards25519 1.1.0 (filippo.io/edwards25519): GO-2026-4503 — filippo.io/edwards25519 is not a DIRECT requirement of this module: go.mod records it as `// indirect`, pulled in transitively, so raise it in place (run `go get filippo.io/edwards25519@v1.1.1`, which updates the require line go.mod already holds for it).
Medium CVE: [GHSA redacted] tools/playground/go.mod— github.com/quic-go/quic-go 0.59.0: [GHSA redacted] — github.com/quic-go/quic-go is not a DIRECT requirement of this module: go.mod records it as `// indirect`, pulled in transitively, so raise it in place (run `go get github.com/quic-go/quic-go@v0.59.1`, which updates the require line go.mod already holds for it).
Medium CVE: [GHSA redacted] go.mod— go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp 1.40.0: [GHSA redacted] — upgrade to 1.43.0
Medium CVE: [GHSA redacted] go.mod— golang.org/x/net 0.49.0: [GHSA redacted] — golang.org/x/net is not a DIRECT requirement of this module: go.mod records it as `// indirect`, pulled in transitively, so raise it in place (run `go get golang.org/x/net@v0.55.0`, which updates the require line go.mod already holds for it). One upgrade of golang.org/x/net 0.49.0 clears all 8 advisories it raises: [GHSA redacted], GO-2026-4918, GO-2026-5025, GO-2026-5026, GO-2026-5027, GO-2026-5029, GO-2026-5030, GO-2026-5942.
Medium CVE: GO-2026-5024 go.mod— golang.org/x/sys 0.41.0 (golang.org/x/sys/windows): GO-2026-5024 — golang.org/x/sys is not a DIRECT requirement of this module: go.mod records it as `// indirect`, pulled in transitively, so raise it in place (run `go get golang.org/x/sys@v0.44.0`, which updates the require line go.mod already holds for it). (in 2 lockfiles)
Medium CVE: GO-2026-5970 go.mod— golang.org/x/text 0.33.0 (golang.org/x/text/unicode/norm): GO-2026-5970 — golang.org/x/text is not a DIRECT requirement of this module: go.mod records it as `// indirect`, pulled in transitively, so raise it in place (run `go get golang.org/x/text@v0.39.0`, which updates the require line go.mod already holds for it).
Medium CVE: [GHSA redacted] sdk/openclaw-adapter/package-lock.json— qs 6.14.2: [GHSA redacted] — qs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin qs to 6.15.2 with an `overrides` entry).
Medium CVE: GO-2026-4864 go.mod— stdlib 1.26.1 (internal/syscall/unix): GO-2026-4864 — fixed in Go 1.26.2; pin a build toolchain at or above it (go.mod `toolchain` directive, or your CI's Go version) — the `go` directive is a minimum language version, not the compiler that builds your binaries. (in 2 lockfiles) One upgrade of stdlib 1.26.1 clears all 19 advisories it raises: GO-2026-4864, GO-2026-4865, GO-2026-4866, GO-2026-4869, GO-2026-4870, GO-2026-4946, GO-2026-4947, GO-2026-4970, GO-2026-4971, GO-2026-4976, GO-2026-4977, GO-2026-4980, GO-2026-4981, GO-2026-4982, GO-2026-4986, GO-2026-5037, GO-2026-5038, GO-2026-5039, GO-2026-5856.
Duplicated block (7 lines × 2) examples/ai-customer-bot/human_review.go:138— examples/ai-customer-bot/human_review.go:138-144 | examples/ai-customer-bot/human_review.go:151-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) internal/agent/job/scheduler.go:175— internal/agent/job/scheduler.go:175-181 | internal/agent/job/scheduler.go:210-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) internal/agent/runtime/executor/invocation.go:33— internal/agent/runtime/executor/invocation.go:33-39 | internal/agent/runtime/executor/step_identity.go:25-31 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) internal/agent/runtime/executor/node_adapter.go:417— internal/agent/runtime/executor/node_adapter.go:417-423 | internal/agent/runtime/executor/node_adapter.go:536-542 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) internal/agent/runtime/executor/node_adapter.go:458— internal/agent/runtime/executor/node_adapter.go:458-464 | internal/agent/runtime/executor/node_adapter.go:513-519 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) internal/agent/runtime/executor/runner.go:1053— internal/agent/runtime/executor/runner.go:1053-1059 | internal/agent/runtime/executor/runner.go:1155-1161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) internal/agent/tools/registry.go:116— internal/agent/tools/registry.go:116-122 | internal/agent/tools/registry.go:142-148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) cmd/cli/main.go:642— cmd/cli/main.go:642-648 | cmd/cli/main.go:691-697 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Hotspot: internal/app/api/app.go internal/app/api/app.go— internal/app/api/app.go changed 4 times in last 90 days, max complexity 195. 1 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: internal/app/worker/app.go internal/app/worker/app.go— internal/app/worker/app.go changed 3 times in last 90 days, max complexity 94.
Hotspot: pkg/config/config.go pkg/config/config.go— pkg/config/config.go changed 5 times in last 90 days, max complexity 33.
Hotspot: internal/agent/runtime/executor/node_adapter.go internal/agent/runtime/executor/node_adapter.go— internal/agent/runtime/executor/node_adapter.go changed 2 times in last 90 days, max complexity 68.
Hotspot: internal/app/api/external_agent_tool.go internal/app/api/external_agent_tool.go— internal/app/api/external_agent_tool.go changed 3 times in last 90 days, max complexity 37.
Hotspot: internal/api/http/handler.go internal/api/http/handler.go— internal/api/http/handler.go changed 3 times in last 90 days, max complexity 33.
Hotspot: internal/app/api/agent_dag.go internal/app/api/agent_dag.go— internal/app/api/agent_dag.go changed 2 times in last 90 days, max complexity 16.
Duplicated block (14 lines × 2) internal/agent/runtime/executor/eino_examples/adapters.go:358— internal/agent/runtime/executor/eino_examples/adapters.go:358-371 | internal/agent/runtime/executor/eino_examples/adapters.go:436-449 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) internal/agent/runtime/executor/rate_limiter.go:70— internal/agent/runtime/executor/rate_limiter.go:70-83 | internal/agent/runtime/executor/rate_limiter.go:109-122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) internal/api/http/handler.go:1254— internal/api/http/handler.go:1254-1267 | internal/api/http/handler.go:1279-1292 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) internal/app/api/agent_dag.go:146— internal/app/api/agent_dag.go:146-159 | internal/app/api/runtime_bridge.go:30-43 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (14 lines × 2) internal/model/llm/ollama.go:121— internal/model/llm/ollama.go:121-134 | internal/model/llm/ollama.go:180-193 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) pkg/routing/router.go:296— pkg/routing/router.go:296-309 | pkg/routing/router.go:367-380 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) internal/api/http/forensics_query.go:322— internal/api/http/forensics_query.go:322-335 | internal/api/http/forensics_query.go:369-382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) internal/agent/runtime/executor/node_adapter.go:499— internal/agent/runtime/executor/node_adapter.go:499-511 | internal/agent/runtime/executor/node_adapter.go:552-565 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) internal/api/http/handler.go:872— internal/api/http/handler.go:872-884 | internal/api/http/handler.go:916-928 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) internal/model/llm/claude.go:123— internal/model/llm/claude.go:123-135 | internal/model/llm/openai.go:131-143 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (13 lines × 2) internal/model/llm/effect_adapter.go:139— internal/model/llm/effect_adapter.go:139-151 | internal/model/llm/effect_adapter.go:286-298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) internal/pipeline/ingest/parser.go:58— internal/pipeline/ingest/parser.go:58-70 | internal/pipeline/ingest/splitter.go:73-85 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (13 lines × 2) internal/splitter/semantic.go:113— internal/splitter/semantic.go:113-125 | internal/splitter/semantic.go:131-143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) pkg/forensics/query_engine.go:138— pkg/forensics/query_engine.go:138-150 | internal/api/http/forensics_query.go:164-176 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) internal/agent/runtime/checkpoint.go:120— internal/agent/runtime/checkpoint.go:120-129 | internal/agent/runtime/checkpoint_pg.go:39-47 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) internal/api/http/handler.go:2780— internal/api/http/handler.go:2780-2788 | internal/api/http/handler.go:2821-2829 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) internal/app/api/app.go:627— internal/app/api/app.go:627-635 | internal/app/worker/app.go:392-400 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) internal/app/bootstrap.go:36— internal/app/bootstrap.go:36-44 | internal/app/worker/app.go:155-163 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) internal/model/llm/effect_adapter.go:75— internal/model/llm/effect_adapter.go:75-84 | internal/model/llm/effect_adapter.go:153-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) cmd/api/main.go:72— cmd/api/main.go:72-79 | cmd/worker/main.go:49-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) internal/agent/runtime/executor/runner.go:409— internal/agent/runtime/executor/runner.go:409-417 | internal/agent/runtime/executor/runner.go:1431-1438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) internal/api/http/handler.go:1487— internal/api/http/handler.go:1487-1494 | internal/api/http/handler.go:1527-1534 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) internal/app/worker/app.go:336— internal/app/worker/app.go:336-343 | internal/app/worker/app.go:528-535 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) pkg/forensics/query_engine.go:98— pkg/forensics/query_engine.go:98-105 | internal/api/http/forensics_query.go:125-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Medium: insecure-hash-algorithm-sha1 examples/customer_support_agent/agent.py:274— Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead.
Medium: math-random-used internal/agent/runtime/contract.go:20— Do not use `math/rand`. Use `crypto/rand` instead. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
Medium: use-tls internal/app/worker/app.go:591— Found an HTTP server without TLS. Use 'http.ListenAndServeTLS' instead. See https://golang.org/pkg/net/http/#ListenAndServeTLS for more information. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: math-random-used pkg/effects/memory.go:19— Do not use `math/rand`. Use `crypto/rand` instead. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
Duplicated block (6 lines × 2) internal/api/http/trace_narrative.go:322— internal/api/http/trace_narrative.go:322-327 | internal/api/http/trace_narrative.go:477-482 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) internal/app/api/node_sink.go:560— internal/app/api/node_sink.go:560-565 | internal/app/api/node_sink.go:578-583 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) internal/runtime/eino/engine.go:251— internal/runtime/eino/engine.go:251-256 | internal/app/models.go:75-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) internal/runtime/jobstore/memory_store.go:274— internal/runtime/jobstore/memory_store.go:274-279 | internal/runtime/jobstore/pgstore.go:385-390 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Change coupling: task_graph.go ↔ router.go internal/agent/planner/task_graph.go— `internal/agent/planner/task_graph.go` and `internal/api/http/router.go` change together 50% of the time (7 of the 14 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: node_adapter.go ↔ memory_store.go internal/agent/runtime/executor/node_adapter.go— `internal/agent/runtime/executor/node_adapter.go` and `internal/runtime/jobstore/memory_store.go` change together 50% of the time (6 of the 12 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: runner.go ↔ store.go internal/agent/runtime/executor/runner.go— `internal/agent/runtime/executor/runner.go` and `internal/runtime/jobstore/store.go` change together 50% of the time (5 of the 10 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
main.main (cognitive 44) cmd/cli/main.go:44— main.main has cognitive complexity 44 (threshold 15). Drivers by points: if/else 38, boolean chains 4, loops 1, match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.main (cognitive 44) examples/streaming/main.go:27— main.main has cognitive complexity 44 (threshold 15). Drivers by points: if/else 33, loops 6, match/switch 4, boolean chains 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (26 lines × 2) internal/runtime/eino/context.go:59— internal/runtime/eino/context.go:59-85 | internal/runtime/eino/engine.go:302-327 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (26 lines × 2) internal/storage/metadata/memory.go:113— internal/storage/metadata/memory.go:113-138 | internal/storage/metadata/memory.go:209-234 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) examples/basic_agent/main.go:35— examples/basic_agent/main.go:35-54 | examples/streaming/main.go:36-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (20 lines × 2) internal/model/llm/gemini.go:91— internal/model/llm/gemini.go:91-110 | internal/model/llm/gemini.go:160-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) internal/pipeline/ingest/splitter.go:173— internal/pipeline/ingest/splitter.go:173-191 | internal/splitter/structural.go:78-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (19 lines × 2) internal/pipeline/ingest/splitter.go:223— internal/pipeline/ingest/splitter.go:223-241 | internal/splitter/structural.go:128-146 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (16 lines × 3) internal/agent/job/pg_store.go:238— internal/agent/job/pg_store.go:238-253 | internal/agent/job/pg_store.go:289-304 | internal/agent/job/pg_store.go:338-353 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 3) internal/agent/runtime/executor/eino_examples/adapters.go:243— internal/agent/runtime/executor/eino_examples/adapters.go:243-258 | internal/agent/runtime/executor/eino_examples/adapters.go:468-483 | internal/agent/runtime/executor/eino_examples/adapters.go:666-681 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 3) internal/agent/job/pg_store.go:526— internal/agent/job/pg_store.go:526-538 | internal/runtime/jobstore/pgstore.go:288-300 | internal/runtime/jobstore/pgstore.go:307-319 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (13 lines × 3) internal/agent/runtime/executor/eino_examples/llm.go:104— internal/agent/runtime/executor/eino_examples/llm.go:104-116 | internal/agent/runtime/executor/eino_examples/llm.go:213-225 | internal/agent/runtime/executor/eino_examples/llm.go:304-316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 3) internal/agent/runtime/executor/runner.go:370— internal/agent/runtime/executor/runner.go:370-378 | internal/agent/runtime/executor/runner.go:822-830 | internal/agent/runtime/executor/runner.go:1408-1416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 3) internal/tool/gatekeeper/gatekeeper.go:373— internal/tool/gatekeeper/gatekeeper.go:373-381 | internal/tool/gatekeeper/gatekeeper.go:388-396 | internal/tool/gatekeeper/gatekeeper.go:411-419 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
api.NewApp (cyclomatic 195) internal/app/api/app.go:135— api.NewApp has cyclomatic complexity 195 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Runner.RunForJob (cyclomatic 191) internal/agent/runtime/executor/runner.go:993— Runner.RunForJob has cyclomatic complexity 191 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
http.BuildNarrative (cyclomatic 103) internal/api/http/trace_narrative.go:114— http.BuildNarrative has cyclomatic complexity 103 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
worker.NewApp (cyclomatic 94) internal/app/worker/app.go:150— worker.NewApp has cyclomatic complexity 94 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Runner.Advance (cyclomatic 93) internal/agent/runtime/executor/runner.go:662— Runner.Advance has cyclomatic complexity 93 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolNodeAdapter.runNodeExecute (cyclomatic 68) internal/agent/runtime/executor/node_adapter.go:579— ToolNodeAdapter.runNodeExecute has cyclomatic complexity 68 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
replayBuilder.BuildFromEvents (cyclomatic 65) internal/agent/replay/replay.go:116— replayBuilder.BuildFromEvents has cyclomatic complexity 65 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolNodeAdapter.runNode (cyclomatic 63) internal/agent/runtime/executor/node_adapter.go:387— ToolNodeAdapter.runNode has cyclomatic complexity 63 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
replayBuilder.applyIncrementalEvents (cyclomatic 62) internal/agent/replay/replay.go:487— replayBuilder.applyIncrementalEvents has cyclomatic complexity 62 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Runner.runParallelLevel (cyclomatic 57) internal/agent/runtime/executor/runner.go:355— Runner.runParallelLevel has cyclomatic complexity 57 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Scheduler.Start (cyclomatic 52) internal/agent/job/scheduler.go:93— Scheduler.Start has cyclomatic complexity 52 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
main.main (cyclomatic 45) cmd/cli/main.go:44— main.main has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EinoNodeAdapter.runNode (cyclomatic 45) internal/agent/runtime/executor/eino_node_adapter.go:63— EinoNodeAdapter.runNode has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
http.BuildExecutionTree (cyclomatic 42) internal/api/http/trace_tree.go:45— http.BuildExecutionTree has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
main.runDebug (cyclomatic 39) cmd/cli/main.go:612— main.runDebug has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
externalAgentCallTool.Execute (cyclomatic 37) internal/app/api/external_agent_tool.go:148— externalAgentCallTool.Execute has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler.AgentMessage (cyclomatic 33) internal/api/http/handler.go:1011— Handler.AgentMessage has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
config.ValidateExternalAgents (cyclomatic 33) pkg/config/config.go:693— config.ValidateExternalAgents has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CustomerServiceBot.classifyIntent (cyclomatic 32) examples/ai-customer-bot/bot.go:153— CustomerServiceBot.classifyIntent has cyclomatic complexity 32 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LLMNodeAdapter.runNode (cyclomatic 31) internal/agent/runtime/executor/node_adapter.go:114— LLMNodeAdapter.runNode has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ingestWorkflowExecutor.Execute (cyclomatic 31) internal/runtime/eino/workflow_executors.go:56— ingestWorkflowExecutor.Execute has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
QueryEngine.Query (cyclomatic 28) pkg/forensics/query_engine.go:73— QueryEngine.Query has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler.ForensicsQuery (cyclomatic 27) internal/api/http/forensics_query.go:61— Handler.ForensicsQuery has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler.JobSignal (cyclomatic 27) internal/api/http/handler.go:1613— Handler.JobSignal has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler.GetJobCognitionTrace (cyclomatic 27) internal/api/http/handler.go:2125— Handler.GetJobCognitionTrace has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MemoryStore.List (cyclomatic 27) internal/storage/metadata/memory.go:95— MemoryStore.List has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
proof.VerifyEvidenceZip (cyclomatic 26) pkg/proof/verify.go:31— proof.VerifyEvidenceZip has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
api.ValidateFrameworkManifest (cyclomatic 25) internal/app/api/framework_manifest.go:117— api.ValidateFrameworkManifest has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
proof.ExportEvidenceZip (cyclomatic 25) pkg/proof/export.go:30— proof.ExportEvidenceZip has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentJobRunner.Start (cyclomatic 24) internal/app/worker/agent_job.go:104— AgentJobRunner.Start has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MemoryStore.Count (cyclomatic 24) internal/storage/metadata/memory.go:191— MemoryStore.Count has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler.GetJobReplay (cyclomatic 23) internal/api/http/handler.go:1838— Handler.GetJobReplay has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
proofLedgerAdapter.ListToolInvocations (cyclomatic 22) internal/api/http/forensics.go:157— proofLedgerAdapter.ListToolInvocations has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler.JobMessage (cyclomatic 22) internal/api/http/handler.go:1737— Handler.JobMessage has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
middleware.NewJWTAuth (cyclomatic 22) internal/api/http/middleware/middleware.go:114— middleware.NewJWTAuth has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MemoryIndexer.Store (cyclomatic 22) internal/pipeline/ingest/eino_indexer.go:63— MemoryIndexer.Store has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
proof.ValidateLedgerConsistency (cyclomatic 22) pkg/proof/verify.go:181— proof.ValidateLedgerConsistency has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
api.HandleACPEvents (cyclomatic 21) internal/api/acp_handler.go:98— api.HandleACPEvents has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentJobRunner.executeJob (cyclomatic 21) internal/app/worker/agent_job.go:227— AgentJobRunner.executeJob has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FrameworkCallableNodeAdapter.runNode (cyclomatic 20) internal/agent/runtime/executor/framework_callable_adapter.go:42— FrameworkCallableNodeAdapter.runNode has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
api.validateProductionRuntimeConfig (cyclomatic 20) internal/app/api/app.go:939— api.validateProductionRuntimeConfig has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
App.Run (cyclomatic 20) internal/app/api/app.go:800— App.Run has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
queryWorkflowExecutor.Execute (cyclomatic 19) internal/runtime/eino/workflow_executors.go:239— queryWorkflowExecutor.Execute has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PatternMatcher.FindSuspiciousPatterns (cyclomatic 19) pkg/ai_forensics/pattern.go:29— PatternMatcher.FindSuspiciousPatterns has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler.GetJobTrace (cyclomatic 18) internal/api/http/handler.go:2001— Handler.GetJobTrace has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EinoRetrieverQueryAdapter.Execute (cyclomatic 18) internal/app/api/adapters.go:103— EinoRetrieverQueryAdapter.Execute has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JobRunner.Start (cyclomatic 17) internal/agent/job/job_runner.go:54— JobRunner.Start has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Compiler.Compile (cyclomatic 17) internal/agent/runtime/executor/compiler.go:54— Compiler.Compile has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler.ListDecisionSignals (cyclomatic 17) internal/api/http/forensics_query.go:609— Handler.ListDecisionSignals has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
config.replaceEnvVars (cyclomatic 17) pkg/config/config.go:789— config.replaceEnvVars has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
main.main (cyclomatic 16) examples/streaming/main.go:27— main.main has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
job.ReclaimOrphanedFromEventStore (cyclomatic 16) internal/agent/job/reclaim.go:28— job.ReclaimOrphanedFromEventStore has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
http.sessionToADKMessages (cyclomatic 16) internal/api/http/handler.go:695— http.sessionToADKMessages has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
api.NewDAGCompilerWithOptions (cyclomatic 16) internal/app/api/agent_dag.go:134— api.NewDAGCompilerWithOptions has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
worker.validateProductionRuntimeConfig (cyclomatic 16) internal/app/worker/app.go:827— worker.validateProductionRuntimeConfig has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
App.Start (cyclomatic 16) internal/app/worker/app.go:562— App.Start has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AnomalyDetector.DetectAnomalies (cyclomatic 16) pkg/ai_forensics/detector.go:64— AnomalyDetector.DetectAnomalies has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
routing.ValidateRouteDecision (cyclomatic 16) pkg/routing/advisor.go:251— routing.ValidateRouteDecision has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FailoverHandler.ExecuteWithFailover (cyclomatic 16) pkg/routing/failover.go:71— FailoverHandler.ExecuteWithFailover has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Runner.RunForJob (cognitive 585) internal/agent/runtime/executor/runner.go:993— Runner.RunForJob has cognitive complexity 585 (threshold 15). Drivers by points: if/else 508, loops 42, boolean chains 33, jumps 2 (nesting depth added 394). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
api.NewApp (cognitive 314) internal/app/api/app.go:135— api.NewApp has cognitive complexity 314 (threshold 15). Drivers by points: if/else 253, boolean chains 47, loops 12, match/switch 2 (nesting depth added 125). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
http.BuildNarrative (cognitive 255) internal/api/http/trace_narrative.go:114— http.BuildNarrative has cognitive complexity 255 (threshold 15). Drivers by points: if/else 215, loops 18, boolean chains 16, match/switch 6 (nesting depth added 171). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
worker.NewApp (cognitive 208) internal/app/worker/app.go:150— worker.NewApp has cognitive complexity 208 (threshold 15). Drivers by points: if/else 181, boolean chains 12, loops 12, match/switch 3 (nesting depth added 112). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler.Start (cognitive 176) internal/agent/job/scheduler.go:93— Scheduler.Start has cognitive complexity 176 (threshold 15). Drivers by points: if/else 149, boolean chains 14, match/switch 7, loops 6 (nesting depth added 123). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Runner.Advance (cognitive 171) internal/agent/runtime/executor/runner.go:662— Runner.Advance has cognitive complexity 171 (threshold 15). Drivers by points: if/else 146, boolean chains 19, loops 6 (nesting depth added 77). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolNodeAdapter.runNode (cognitive 124) internal/agent/runtime/executor/node_adapter.go:387— ToolNodeAdapter.runNode has cognitive complexity 124 (threshold 15). Drivers by points: if/else 112, boolean chains 10, match/switch 2 (nesting depth added 70). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
replayBuilder.BuildFromEvents (cognitive 117) internal/agent/replay/replay.go:116— replayBuilder.BuildFromEvents has cognitive complexity 117 (threshold 15). Drivers by points: if/else 93, boolean chains 12, match/switch 11, loops 1 (nesting depth added 66). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
replayBuilder.applyIncrementalEvents (cognitive 114) internal/agent/replay/replay.go:487— replayBuilder.applyIncrementalEvents has cognitive complexity 114 (threshold 15). Drivers by points: if/else 91, boolean chains 11, match/switch 11, loops 1 (nesting depth added 66). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
http.BuildExecutionTree (cognitive 112) internal/api/http/trace_tree.go:45— http.BuildExecutionTree has cognitive complexity 112 (threshold 15). Drivers by points: if/else 105, match/switch 4, boolean chains 2, loops 1 (nesting depth added 76). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Runner.runParallelLevel (cognitive 106) internal/agent/runtime/executor/runner.go:355— Runner.runParallelLevel has cognitive complexity 106 (threshold 15). Drivers by points: if/else 77, loops 22, boolean chains 7 (nesting depth added 49). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolNodeAdapter.runNodeExecute (cognitive 90) internal/agent/runtime/executor/node_adapter.go:579— ToolNodeAdapter.runNodeExecute has cognitive complexity 90 (threshold 15). Drivers by points: if/else 70, boolean chains 19, loops 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.runDebug (cognitive 88) cmd/cli/main.go:612— main.runDebug has cognitive complexity 88 (threshold 15). Drivers by points: if/else 78, boolean chains 6, loops 4 (nesting depth added 48). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MemoryStore.List (cognitive 81) internal/storage/metadata/memory.go:95— MemoryStore.List has cognitive complexity 81 (threshold 15). Drivers by points: if/else 61, loops 17, boolean chains 3 (nesting depth added 55). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.AgentMessage (cognitive 78) internal/api/http/handler.go:1011— Handler.AgentMessage has cognitive complexity 78 (threshold 15). Drivers by points: if/else 75, boolean chains 3 (nesting depth added 43). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EinoNodeAdapter.runNode (cognitive 76) internal/agent/runtime/executor/eino_node_adapter.go:63— EinoNodeAdapter.runNode has cognitive complexity 76 (threshold 15). Drivers by points: if/else 58, boolean chains 14, loops 4 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MemoryStore.Count (cognitive 76) internal/storage/metadata/memory.go:191— MemoryStore.Count has cognitive complexity 76 (threshold 15). Drivers by points: if/else 56, loops 17, boolean chains 3 (nesting depth added 53). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
config.ValidateExternalAgents (cognitive 59) pkg/config/config.go:693— config.ValidateExternalAgents has cognitive complexity 59 (threshold 15). Drivers by points: if/else 46, boolean chains 8, match/switch 4, loops 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentJobRunner.Start (cognitive 57) internal/app/worker/agent_job.go:104— AgentJobRunner.Start has cognitive complexity 57 (threshold 15). Drivers by points: if/else 39, match/switch 14, boolean chains 3, loops 1 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
proof.VerifyEvidenceZip (cognitive 49) pkg/proof/verify.go:31— proof.VerifyEvidenceZip has cognitive complexity 49 (threshold 15). Drivers by points: if/else 44, boolean chains 3, loops 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
externalAgentCallTool.Execute (cognitive 47) internal/app/api/external_agent_tool.go:148— externalAgentCallTool.Execute has cognitive complexity 47 (threshold 15). Drivers by points: if/else 43, match/switch 3, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MemoryIndexer.Store (cognitive 44) internal/pipeline/ingest/eino_indexer.go:63— MemoryIndexer.Store has cognitive complexity 44 (threshold 15). Drivers by points: if/else 36, loops 5, boolean chains 3 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ingestWorkflowExecutor.Execute (cognitive 44) internal/runtime/eino/workflow_executors.go:56— ingestWorkflowExecutor.Execute has cognitive complexity 44 (threshold 15). Drivers by points: if/else 44 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
proof.ValidateLedgerConsistency (cognitive 42) pkg/proof/verify.go:181— proof.ValidateLedgerConsistency has cognitive complexity 42 (threshold 15). Drivers by points: if/else 34, boolean chains 4, loops 4 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LLMNodeAdapter.runNode (cognitive 41) internal/agent/runtime/executor/node_adapter.go:114— LLMNodeAdapter.runNode has cognitive complexity 41 (threshold 15). Drivers by points: if/else 31, boolean chains 10 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QueryEngine.Query (cognitive 40) pkg/forensics/query_engine.go:73— QueryEngine.Query has cognitive complexity 40 (threshold 15). Drivers by points: if/else 30, boolean chains 8, loops 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
proofLedgerAdapter.ListToolInvocations (cognitive 39) internal/api/http/forensics.go:157— proofLedgerAdapter.ListToolInvocations has cognitive complexity 39 (threshold 15). Drivers by points: if/else 34, loops 3, boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.ForensicsQuery (cognitive 38) internal/api/http/forensics_query.go:61— Handler.ForensicsQuery has cognitive complexity 38 (threshold 15). Drivers by points: if/else 30, loops 5, boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.GetJobCognitionTrace (cognitive 38) internal/api/http/handler.go:2125— Handler.GetJobCognitionTrace has cognitive complexity 38 (threshold 15). Drivers by points: if/else 28, boolean chains 5, loops 5 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
api.ValidateFrameworkManifest (cognitive 37) internal/app/api/framework_manifest.go:117— api.ValidateFrameworkManifest has cognitive complexity 37 (threshold 15). Drivers by points: if/else 33, loops 2, match/switch 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.JobSignal (cognitive 34) internal/api/http/handler.go:1613— Handler.JobSignal has cognitive complexity 34 (threshold 15). Drivers by points: if/else 29, boolean chains 4, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.GetJobTrace (cognitive 34) internal/api/http/handler.go:2001— Handler.GetJobTrace has cognitive complexity 34 (threshold 15). Drivers by points: if/else 29, boolean chains 3, loops 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
proof.ExportEvidenceZip (cognitive 34) pkg/proof/export.go:30— proof.ExportEvidenceZip has cognitive complexity 34 (threshold 15). Drivers by points: if/else 33, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PatternMatcher.FindSuspiciousPatterns (cognitive 33) pkg/ai_forensics/pattern.go:29— PatternMatcher.FindSuspiciousPatterns has cognitive complexity 33 (threshold 15). Drivers by points: if/else 29, loops 3, boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SemanticSplitter.mergeBySemantics (cognitive 31) internal/splitter/semantic.go:100— SemanticSplitter.mergeBySemantics has cognitive complexity 31 (threshold 15). Drivers by points: if/else 28, boolean chains 2, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JobRunner.Start (cognitive 30) internal/agent/job/job_runner.go:54— JobRunner.Start has cognitive complexity 30 (threshold 15). Drivers by points: if/else 22, boolean chains 5, match/switch 2, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.GetJobReplay (cognitive 30) internal/api/http/handler.go:1838— Handler.GetJobReplay has cognitive complexity 30 (threshold 15). Drivers by points: if/else 22, boolean chains 3, loops 3, match/switch 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentJobRunner.executeJob (cognitive 30) internal/app/worker/agent_job.go:227— AgentJobRunner.executeJob has cognitive complexity 30 (threshold 15). Drivers by points: if/else 18, match/switch 7, boolean chains 3, loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
config.replaceEnvVars (cognitive 30) pkg/config/config.go:789— config.replaceEnvVars has cognitive complexity 30 (threshold 15). Drivers by points: if/else 26, loops 4 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Builder.BuildFromEvents (cognitive 30) pkg/evidence/builder.go:30— Builder.BuildFromEvents has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16, loops 13, boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.JobMessage (cognitive 29) internal/api/http/handler.go:1737— Handler.JobMessage has cognitive complexity 29 (threshold 15). Drivers by points: if/else 24, boolean chains 3, loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EinoRetrieverQueryAdapter.Execute (cognitive 28) internal/app/api/adapters.go:103— EinoRetrieverQueryAdapter.Execute has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16, match/switch 6, loops 4, boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App.Run (cognitive 28) internal/app/api/app.go:800— App.Run has cognitive complexity 28 (threshold 15). Drivers by points: if/else 21, boolean chains 5, match/switch 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
worker.initMCPManager (cognitive 28) internal/app/worker/app.go:888— worker.initMCPManager has cognitive complexity 28 (threshold 15). Drivers by points: if/else 25, loops 2, boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FailoverHandler.ExecuteWithFailover (cognitive 28) pkg/routing/failover.go:71— FailoverHandler.ExecuteWithFailover has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15, match/switch 11, boolean chains 1, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TaskGraphExecutor.executeNode (cognitive 26) internal/agent/planner/executor.go:66— TaskGraphExecutor.executeNode has cognitive complexity 26 (threshold 15). Drivers by points: if/else 25, match/switch 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LLMPlanner.PlanGoal (cognitive 26) internal/agent/planner/planner.go:178— LLMPlanner.PlanGoal has cognitive complexity 26 (threshold 15). Drivers by points: if/else 21, loops 4, boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Compiler.Compile (cognitive 26) internal/agent/runtime/executor/compiler.go:54— Compiler.Compile has cognitive complexity 26 (threshold 15). Drivers by points: if/else 20, loops 4, boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.ListDecisionSignals (cognitive 26) internal/api/http/forensics_query.go:609— Handler.ListDecisionSignals has cognitive complexity 26 (threshold 15). Drivers by points: if/else 20, loops 3, match/switch 2, boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
middleware.NewJWTAuth (cognitive 26) internal/api/http/middleware/middleware.go:114— middleware.NewJWTAuth has cognitive complexity 26 (threshold 15). Drivers by points: if/else 22, boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentFactory.collectTools (cognitive 26) internal/runtime/eino/agent_factory.go:186— AgentFactory.collectTools has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16, loops 10 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomerServiceBot.RunInteractiveSession (cognitive 25) examples/ai-customer-bot/bot.go:384— CustomerServiceBot.RunInteractiveSession has cognitive complexity 25 (threshold 15). Drivers by points: if/else 18, loops 5, match/switch 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MemoryPipeline.Compress (cognitive 25) internal/storage/vector/pipeline/pipeline.go:303— MemoryPipeline.Compress has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17, loops 8 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnomalyDetector.DetectAnomalies (cognitive 25) pkg/ai_forensics/detector.go:64— AnomalyDetector.DetectAnomalies has cognitive complexity 25 (threshold 15). Drivers by points: if/else 21, boolean chains 3, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Runner.nextRunnableBatch (cognitive 24) internal/agent/runtime/executor/runner.go:316— Runner.nextRunnableBatch has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14, loops 7, boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
api.HandleACPEvents (cognitive 24) internal/api/acp_handler.go:98— api.HandleACPEvents has cognitive complexity 24 (threshold 15). Drivers by points: if/else 19, match/switch 3, boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
job.ReclaimOrphanedFromEventStore (cognitive 23) internal/agent/job/reclaim.go:28— job.ReclaimOrphanedFromEventStore has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16, boolean chains 4, match/switch 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
executor.TopoOrder (cognitive 23) internal/agent/runtime/executor/steppable.go:34— executor.TopoOrder has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15, loops 7, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
http.sessionToADKMessages (cognitive 23) internal/api/http/handler.go:695— http.sessionToADKMessages has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13, loops 5, boolean chains 3, match/switch 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
http.parseStateChanges (cognitive 23) internal/api/http/trace_narrative.go:537— http.parseStateChanges has cognitive complexity 23 (threshold 15). Drivers by points: if/else 21, boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.handleApprovalAction (cognitive 23) internal/api/http/handler.go:2820— Handler.handleApprovalAction has cognitive complexity 23 (threshold 15). Drivers by points: if/else 23 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Retriever.retrieve (cognitive 23) internal/pipeline/query/retriever.go:116— Retriever.retrieve has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15, loops 6, boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.main (cognitive 22) examples/eino_stateful/main.go:223— main.main has cognitive complexity 22 (threshold 15). Drivers by points: if/else 21, loops 1 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
App.triggerSnapshotsForHighEventJobs (cognitive 22) internal/app/worker/app.go:649— App.triggerSnapshotsForHighEventJobs has cognitive complexity 22 (threshold 15). Drivers by points: if/else 19, boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MemoryStore.Search (cognitive 22) internal/storage/vector/memory.go:85— MemoryStore.Search has cognitive complexity 22 (threshold 15). Drivers by points: if/else 17, loops 4, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.runChat (cognitive 21) cmd/cli/main.go:271— main.runChat has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16, loops 3, boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ManusAgentAdapter.Invoke (cognitive 21) internal/agent/runtime/executor/eino_examples/adapters.go:545— ManusAgentAdapter.Invoke has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16, loops 4, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
api.SessionToADKMessages (cognitive 21) internal/app/api/adk_agent.go:69— api.SessionToADKMessages has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13, loops 5, boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
queryWorkflowExecutor.Execute (cognitive 21) internal/runtime/eino/workflow_executors.go:239— queryWorkflowExecutor.Execute has cognitive complexity 21 (threshold 15). Drivers by points: if/else 17, boolean chains 4 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ACPClient.doPostWithRetry (cognitive 21) internal/runtime/hermes/acp_client.go:206— ACPClient.doPostWithRetry has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16, match/switch 3, boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FrameworkCallableNodeAdapter.runNode (cognitive 20) internal/agent/runtime/executor/framework_callable_adapter.go:42— FrameworkCallableNodeAdapter.runNode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 17, boolean chains 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
IPAllowList.getClientIP (cognitive 20) internal/api/http/middleware/iplist.go:103— IPAllowList.getClientIP has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14, loops 5, boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App.runIngestQueueLoop (cognitive 20) internal/app/worker/app.go:989— App.runIngestQueueLoop has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16, match/switch 2, boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HermesRunner.waitForCompletion (cognitive 20) internal/runtime/eino/hermes_runner.go:135— HermesRunner.waitForCompletion has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13, match/switch 5, boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomerServiceBot.classifyIntent (cognitive 19) examples/ai-customer-bot/bot.go:153— CustomerServiceBot.classifyIntent has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 8, loops 2, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.main (cognitive 19) examples/eino_agent_with_tools/main.go:138— main.main has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16, loops 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
executor.LevelGroups (cognitive 19) internal/agent/runtime/executor/steppable.go:86— executor.LevelGroups has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11, loops 8 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolNodeAdapter.runConfirmation (cognitive 19) internal/agent/runtime/executor/node_adapter.go:324— ToolNodeAdapter.runConfirmation has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17, boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolRateLimiter.Wait (cognitive 19) internal/agent/runtime/executor/rate_limiter.go:92— ToolRateLimiter.Wait has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17, match/switch 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
http.buildTraceHTML (cognitive 19) internal/api/http/handler.go:2271— http.buildTraceHTML has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16, loops 2, boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
api.NewDAGCompilerWithOptions (cognitive 19) internal/app/api/agent_dag.go:134— api.NewDAGCompilerWithOptions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, boolean chains 1 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
App.Start (cognitive 19) internal/app/worker/app.go:562— App.Start has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, boolean chains 5 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocumentSplitter.mergeAndSplit (cognitive 19) internal/pipeline/ingest/splitter.go:194— DocumentSplitter.mergeAndSplit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
eino.schemaMapToParams (cognitive 19) internal/runtime/eino/tool_bridge.go:129— eino.schemaMapToParams has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, loops 5 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
jobstore.gcToolInvocations (cognitive 19) internal/runtime/jobstore/gc.go:82— jobstore.gcToolInvocations has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pgStore.Watch (cognitive 19) internal/runtime/jobstore/pgstore.go:322— pgStore.Watch has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8, match/switch 6, loops 4, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StructuralSplitter.mergeAndSplit (cognitive 19) internal/splitter/structural.go:99— StructuralSplitter.mergeAndSplit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
proof.extractJobMetadata (cognitive 19) pkg/proof/export.go:253— proof.extractJobMetadata has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, boolean chains 2, match/switch 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
routing.ValidateRouteDecision (cognitive 19) pkg/routing/advisor.go:251— routing.ValidateRouteDecision has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17, loops 2 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DEERAgent.Invoke (cognitive 18) internal/agent/runtime/executor/eino_agent/agent.go:187— DEERAgent.Invoke has cognitive complexity 18 (threshold 15). Drivers by points: if/else 15, boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphAdapter.Invoke (cognitive 18) internal/agent/runtime/executor/eino_examples/adapters.go:861— GraphAdapter.Invoke has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14, loops 4 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HermesDispatchTool.Execute (cognitive 18) internal/agent/tools/hermes_dispatch.go:150— HermesDispatchTool.Execute has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, loops 4, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.AgentResumeCheckpoint (cognitive 18) internal/api/http/handler.go:801— Handler.AgentResumeCheckpoint has cognitive complexity 18 (threshold 15). Drivers by points: if/else 15, boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MemoryRetriever.Retrieve (cognitive 18) internal/pipeline/query/eino_retriever.go:69— MemoryRetriever.Retrieve has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12, loops 4, boolean chains 2 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LongTextPipeline.normalizeInput (cognitive 18) internal/pipeline/specialized/longtext.go:125— LongTextPipeline.normalizeInput has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14, loops 3, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.main (cognitive 17) examples/eino_chain/main.go:139— main.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, boolean chains 3, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Agent.runInternal (cognitive 17) internal/agent/agent.go:95— Agent.runInternal has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, loops 3, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TaskGraphExecution.TopologicalSort (cognitive 17) internal/agent/domain/task_graph.go:138— TaskGraphExecution.TopologicalSort has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, loops 6 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReactAgentAdapter.Invoke (cognitive 17) internal/agent/runtime/executor/eino_examples/adapters.go:113— ReactAgentAdapter.Invoke has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, loops 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
api.validateProductionRuntimeConfig (cognitive 17) internal/app/api/app.go:939— api.validateProductionRuntimeConfig has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 7. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
pgStore.Append (cognitive 17) internal/runtime/jobstore/pgstore.go:101— pgStore.Append has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15, boolean chains 2 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DistributedVerifier.VerifyAcrossOrgs (cognitive 17) pkg/distributed/verifier.go:51— DistributedVerifier.VerifyAcrossOrgs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14, loops 2, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AutoDetectPolicy.Apply (cognitive 17) pkg/redaction/detector.go:237— AutoDetectPolicy.Apply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, match/switch 4, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JobStoreMem.ClaimNextPendingForWorker (cognitive 16) internal/agent/job/job_store.go:232— JobStoreMem.ClaimNextPendingForWorker has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 4, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JobStorePg.ListByAgent (cognitive 16) internal/agent/job/pg_store.go:313— JobStorePg.ListByAgent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ManusAgent.Invoke (cognitive 16) internal/agent/runtime/executor/eino_agent/agent.go:342— ManusAgent.Invoke has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, loops 4, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SSETransport.handleSSEEvent (cognitive 16) internal/agent/tools/mcp/transport_sse.go:160— SSETransport.handleSSEEvent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, match/switch 3, boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
api.HandleACPCheckpoints (cognitive 16) internal/api/acp_handler.go:246— api.HandleACPCheckpoints has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
middleware.parseIPList (cognitive 16) internal/api/http/middleware/iplist.go:65— middleware.parseIPList has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
nodeEventSinkImpl.AppendToolInvocationFinished (cognitive 16) internal/app/api/node_sink.go:311— nodeEventSinkImpl.AppendToolInvocationFinished has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, match/switch 2, boolean chains 1 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ingest.extractPDFText (cognitive 16) internal/pipeline/ingest/pdf.go:32— ingest.extractPDFText has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HTTPTool.Execute (cognitive 16) internal/tool/builtin/http.go:135— HTTPTool.Execute has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, boolean chains 2, loops 2 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
memorySystem.Execute (cognitive 16) pkg/effects/memory.go:33— memorySystem.Execute has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 26 floating ref(s) across 6 workflow file(s): `actions/checkout@v4` (.github/workflows/slsa-release.yml:29), `actions/setup-go@v5` (.github/workflows/slsa-release.yml:35), `slsa-framework/slsa-github-generator/annotations@v2.0.0` (.github/workflows/slsa-release.yml:61), `actions/upload-release-asset@v1` (.github/workflows/slsa-release.yml:71), `actions/github-script@v7` (.github/workflows/pr-serial-gate.yml:18), `actions/checkout@v4` (.github/workflows/monthly-release.yml:26), `actions/setup-go@v5` (.github/workflows/monthly-release.yml:31), `actions/checkout@v4` (.github/workflows/homepage-pages.yml:28), … (+18 more)
D36 · Supply-chain Provenance & Signing· PR-triggered workflow without a permissions block · ×1
PR-triggered workflow without a permissions block — 2 workflow(s) triggered by pull_request declare no `permissions:` block (dependency-review.yml, ci.yml) and so run with the repository's default GITHUB_TOKEN scope, while sibling workflows in the same repository are already scoped. Pull-request runs build the least-trusted code in the repository; give each of these workflows its own least-privilege block — `permissions: {contents: read}` at the top of the workflow, widened per job only where a job genuinely writes.
Duplicated block (18 lines × 2) internal/model/llm/openai.go:95— internal/model/llm/openai.go:95-112 | internal/model/llm/openai.go:158-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 3) internal/agent/job/pg_store.go:189— internal/agent/job/pg_store.go:189-205 | internal/agent/job/pg_store.go:233-249 | internal/agent/job/pg_store.go:284-300 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 4) examples/eino_agent_with_tools/main.go:138— examples/eino_agent_with_tools/main.go:138-154 | examples/eino_chain/main.go:139-154 | examples/eino_stateful/main.go:223-239 | examples/ollama/main.go:67-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (16 lines × 2) internal/api/acp_handler.go:101— internal/api/acp_handler.go:101-116 | internal/api/acp_handler.go:249-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 3) internal/agent/runtime/executor/eino_agent/agent.go:125— internal/agent/runtime/executor/eino_agent/agent.go:125-139 | internal/agent/runtime/executor/eino_agent/agent.go:283-297 | internal/agent/runtime/executor/eino_agent/agent.go:442-456 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 6) internal/agent/instance/store_pg.go:34— internal/agent/instance/store_pg.go:34-46 | internal/agent/job/pg_store.go:47-59 | internal/agent/memory/episodic_pg.go:33-45 | internal/agent/memory/longterm_pg.go:32-44 | internal/agent/messaging/store_pg.go:34-46 | internal/agent/runtime/state_pg.go:33-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (12 lines × 4) internal/pipeline/ingest/embedding.go:54— internal/pipeline/ingest/embedding.go:54-65 | internal/pipeline/ingest/indexer.go:95-106 | internal/pipeline/ingest/parser.go:57-68 | internal/pipeline/ingest/splitter.go:72-83 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (11 lines × 5) internal/api/http/handler.go:2107— internal/api/http/handler.go:2107-2117 | internal/api/http/handler.go:2148-2159 | internal/api/http/handler.go:2166-2177 | internal/api/http/handler.go:2205-2215 | internal/api/http/handler.go:2287-2297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 4) internal/agent/runtime/executor/eino_agent/agent.go:478— internal/agent/runtime/executor/eino_agent/agent.go:478-488 | internal/agent/runtime/executor/eino_examples/adapters.go:224-234 | internal/agent/runtime/executor/eino_examples/adapters.go:453-463 | internal/agent/runtime/executor/eino_examples/adapters.go:651-661 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 3) internal/agent/runtime/checkpoint.go:95— internal/agent/runtime/checkpoint.go:95-102 | internal/agent/runtime/checkpoint.go:121-129 | internal/agent/runtime/checkpoint_pg.go:40-47 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (6 lines × 4) pkg/tracing/otel.go:288— pkg/tracing/otel.go:288-293 | pkg/tracing/otel.go:323-328 | pkg/tracing/otel.go:379-384 | pkg/tracing/otel.go:428-433 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 3) internal/agent/runtime/executor/framework_callable_adapter.go:126— internal/agent/runtime/executor/framework_callable_adapter.go:126-131 | internal/agent/runtime/executor/node_adapter.go:819-824 | internal/agent/runtime/executor/node_adapter.go:887-892 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Low: dynamic-urllib-use-detected examples/customer_support_agent/demo.py:196— Detected a dynamic value being used with urllib. urllib supports 'file://' schemes, so a dynamic value controlled by a malicious actor may allow them to read arbitrary files. Audit uses of urllib calls to ensure user data cannot control the URLs, or consider using the 'requests' library instead. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Low: cookie-missing-httponly internal/api/http/middleware/oidc.go:149— A session cookie was detected without setting the 'HttpOnly' flag. The 'HttpOnly' flag for cookies instructs the browser to forbid client-side scripts from reading the cookie which mitigates XSS attacks. Set the 'HttpOnly' flag by setting 'HttpOnly' to 'true' in the Cookie. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Low: cookie-missing-secure internal/api/http/middleware/oidc.go:149— A session cookie was detected without setting the 'Secure' flag. The 'secure' flag for cookies prevents the client from transmitting the cookie over insecure channels such as HTTP. Set the cookie's Secure flag on the cookie value your language's API exposes — and set it to a condition, not a constant, where the same handler also serves plaintext requests. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Low: grpc-server-insecure-connection internal/app/api/app.go:1023— Found an insecure gRPC server without 'grpc.Creds()' or options with credentials. This allows for a connection without encryption to this server. A malicious attacker could tamper with the gRPC message, which could compromise the machine. Include credentials derived from an SSL certificate in order to create a secure gRPC connection. You can create credentials using 'credentials.NewServerTLSFromFile("cert.pem", "cert.key")'. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Low: dynamic-urllib-use-detected sdk/python/aetheris/integrations/embedded.py:139— Detected a dynamic value being used with urllib. urllib supports 'file://' schemes, so a dynamic value controlled by a malicious actor may allow them to read arbitrary files. Audit uses of urllib calls to ensure user data cannot control the URLs, or consider using the 'requests' library instead. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 13 significant file(s) lose their only recent owner: templates/autonomous-researcher/workflow.go, templates/multi-agent-debate/workflow.go, tools/mcp-gateway/tools/mcp-filesystem/tool.go, tools/mcp-gateway/tools/mcp-database/tool.go, internal/api/acp_handler.go, sdk/python/aetheris/client.py, internal/app/api/external_agent_tool.go, templates/rag-assistant/workflow.go (+5 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 7 significant file(s) lose their only recent owner: internal/agent/runtime/executor/eino_agent/agent.go, internal/runtime/eino/tools.go, internal/tool/mcp/server.go, internal/agent/runtime/checkpoint.go, internal/agent/runtime/checkpoint_pg.go, internal/agent/executor/executor.go, internal/agent/planner/executor.go. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 4 significant file(s) lose their only recent owner: pkg/compliance/hipaa.go, pkg/log/logger.go, internal/app/api/pool_manager.go, internal/model/llm/interface.go. Pair on, review, or document these before any departure.
Low CVE: [GHSA redacted] sdk/openclaw-adapter/package-lock.json— @babel/core 7.29.0: [GHSA redacted] — @babel/core is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/core to 7.29.6 with an `overrides` entry).
Low CVE: [GHSA redacted] sdk/openclaw-adapter/package-lock.json— body-parser 1.20.5: [GHSA redacted] — body-parser is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin body-parser to 1.20.6 with an `overrides` entry).
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.go, .ts) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D19 · Documentation Quality· The 'Without Aetheris · ×1
The 'Without Aetheris: retry → email sent twice' failure mode is mentioned but never verified by code or test. README.md— Add a short verification snippet showing this exact behavior, such as a repeated call that asserts the same Idempotency-Key returns the same result.
D19 · Documentation Quality· The 'Quick verification · ×1
The 'Quick verification: ... make docker-run' section is ideal but the full command line and how to run benchmarks is cut off mid-sentence. README.md— Keep the clip; the visible portion is clear, so no action needed.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Rotate the exposed credentials — git history can't be un-committed — Some of these secrets are in git HISTORY: deleting the file does not remove them (the commit persists on every clone, fork and backup). The remediation is to ROTATE each historically-exposed credential and treat it as compromised — not to delete the file. Rewriting history is disruptive and unreliable across existing forks. (Working-tree-only secrets — no commit — can instead be removed from the file and moved to a secret store.)
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 64 of 254 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it. None is large enough to schedule a dedicated read-through on its own, so they are folded into the freshness score rather than raised individually — largest first: pkg/routing/model.go, internal/agent/domain/task_graph.go, internal/runtime/eino/run_store.go (and 61 more).
D36 · Supply-chain Provenance & Signing· No SBOM · ×1
No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (`cyclonedx-gomod` over the module graph — or Go's own build info, which already records the module set in the binary, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Publish it as a release asset (`*.spdx.json` / `*.cdx.json`) so consumers can see what they are installing.
D37 · Vulnerability-disclosure Policy· Disclosure policy has no reporting contact · ×1
Disclosure policy has no reporting contact — SECURITY.md is present but no reporting contact (email / URL / mailto) was found — a coordinated-disclosure policy must tell reporters where to send a report.
Coverage not included — suite not readable by the collector — Coverage NOT READ here — but this repository measures it: a coverage step in CI (`go test -coverprofile`) show(s) coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.go, .ts), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored.
Info — 2 finding(s)
D12 · Dependency Hygiene· Dependency hygiene not measured · ×1
Dependency hygiene not measured — dependency manifest found but not parsed for hygiene — This repository's dependency manifest (a Go module (go.mod/go.sum)) was found, but this pass cannot parse it for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D38 wherever the manifest is OSV-readable.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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.
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.
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
—
Run 019fafcf-847a-7141-91d0-616cc8b20c05 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 61 · Warnings: 326 · Recommendations: 21 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 29-07-2026 @ 21:37 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.