Public report — goakt, 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.
218findings with an exact file:lineof 231 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
26/95dimensions across the health lenses75649 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.
Tochemey/goakt is in good health (75%). It can be evolved and depended on with normal engineering discipline; the items below are improvements, not blockers.
It is strongest in Architecture (99%) — the structure is clean and changes stay contained. Code Health (82%) is solid too.
Leadership focus, highest impact first: Stamp a version in your build/package manifest (e.g. csproj <Version> (Release Hygiene); 'Testing' section to the root README (Documentation (README)); Start an ADR log (docs/adr/) recording significant decisions… (Architecture documentation).
For scale: Medium (~75,649 production lines); rebuilding it from scratch would take roughly ~1.8 person-years (~1–4 engineers). Approximate, ±~30%.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
1.1× (at 75% 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 ~1.8 person-years of build effort (about ~€260,000 to rebuild). Its weakest lens is Readiness at 71% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 1.1× 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 1 Off-boarding risk finding(s) in Bus Factor.
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.
Of everything flagged, the best return on effort is: 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. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ 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.
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
A05:2021 — Security Misconfiguration
8
High / Critical
A06:2021 — Vulnerable & Outdated Components
1
Medium
Roadmap
First, establish release hygiene by stamping a version in your build manifest or tagging releases with semver to ensure all builds are traceable. Next, improve documentation by adding a 'Testing' section to the root README to explain how to run the test suite. Then, begin an ADR log in docs/adr/ to record significant architectural decisions and their rationale. Finally, address the single off-boarding risk identified in the Bus Factor and resolve the network egress confinement issue to strengthen security posture.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.
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.
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. 25 of 26 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 1 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 — 26 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, 218 of 231 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
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.
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.
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.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
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".
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 (2): 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.
33 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was actorSystem.remoteSpawnHandler at 23. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being replicatorActor.handleMessage at 20 — they are counted neither in the figure above nor in this dimension's score.
+ 28 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 actorSystem.remoteSpawnHandler (cyclomatic 23) finding(s) in Cyclomatic Complexity — start with remote_server.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 flowActor.Receive (cyclomatic 22) finding(s) in Cyclomatic Complexity — start with stage_flow.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 ProtoServer.handleConn (cyclomatic 21) finding(s) in Cyclomatic Complexity — start with proto_server.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.
+ 58 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 WorkerPool.cleanup (cognitive 64) finding(s) in Cognitive Complexity — start with worker_pool.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 ProtoServer.handleConn (cognitive 43) finding(s) in Cognitive Complexity — start with proto_server.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 flowActor.Receive (cognitive 42) finding(s) in Cognitive Complexity — start with stage_flow.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 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 Factor5.1 / 10Adequate✓ 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.
133 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is actor/actor_system.go.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
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.
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 IaC: DS-0002 · ×3Dockerfile.toolsdetected by trivy finding
Medium IaC: KSV-0001 · ×3playground/issue-1260/deploy/k8s.yamldetected by trivy finding
Low IaC: KSV-0003 · ×2playground/issue-1260/deploy/k8s.yamldetected by trivy finding
What to do
Resolve the 3 High IaC finding(s) in IaC & Container Security — start with Dockerfile.tools, Dockerfile, k8s.yaml. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with k8s.yaml (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with k8s.yaml (2). — One of this dimension's main actionable groups (2 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.
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 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No artifact signing 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.
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.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No AppArmor/SELinux confinement finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 69 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — 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 — ~98706 lines of test source are present (.go) 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.
D19 Documentation Quality — LLM evaluation failed
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.go) 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 — no ADRs to check
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.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to 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.
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
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, 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.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.go) 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 Domain Modelling — applicable but not scored (2 of 2 signals for this style — below the bar we score at): 4 aggregate root(s) (AggregateRoot/IAggregateRoot); 5 value object(s)
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this check looks for (7 event-sourced shape(s) (event folds / event-recording aggregates))
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this check looks for (6 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
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.
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.
Hotspot: actor/actor_system.go actor/actor_system.go— actor/actor_system.go changed 24 times in last 90 days, max complexity 18. 5 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: actor/pid.go actor/pid.go— actor/pid.go changed 14 times in last 90 days, max complexity 20. 3 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: actor/remote_server.go actor/remote_server.go— actor/remote_server.go changed 11 times in last 90 days, max complexity 23. 3 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: actor/grain_engine.go actor/grain_engine.go— actor/grain_engine.go changed 8 times in last 90 days, max complexity 19. 1 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: stream/stage_source_ref.go stream/stage_source_ref.go— stream/stage_source_ref.go changed 2 times in last 90 days, max complexity 19.
Hotspot: actor/router.go actor/router.go— actor/router.go changed 2 times in last 90 days, max complexity 18. 1 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: stream/stage_partition.go stream/stage_partition.go— stream/stage_partition.go changed 2 times in last 90 days, max complexity 17.
Hotspot: stream/stage_subflow.go stream/stage_subflow.go— stream/stage_subflow.go changed 2 times in last 90 days, max complexity 17.
Hotspot: stream/stage_sink_ref.go stream/stage_sink_ref.go— stream/stage_sink_ref.go changed 2 times in last 90 days, max complexity 15.
Duplicated block (12 lines × 2) actor/cluster_singleton.go:148— actor/cluster_singleton.go:148-159 | actor/spawn.go:721-732 — 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 (12 lines × 2) actor/grain_context.go:435— actor/grain_context.go:435-446 | actor/grain_context.go:488-500 — 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) actor/grain_engine.go:1336— actor/grain_engine.go:1336-1349 | actor/grain_engine.go:1383-1394 — 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) actor/remote_server.go:1518— actor/remote_server.go:1518-1529 | actor/remote_server.go:1541-1552 — 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) actor/remote_watch_registry.go:168— actor/remote_watch_registry.go:168-179 | actor/remote_watch_registry.go:314-325 — 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) actor/remote_watch_registry.go:265— actor/remote_watch_registry.go:265-276 | actor/remote_watch_registry.go:332-343 — 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) stream/stage_flow.go:290— stream/stage_flow.go:290-301 | stream/stage_parallel.go:206-217 — 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 (12 lines × 2) stream/stage_flow.go:397— stream/stage_flow.go:397-408 | stream/stage_flow.go:530-541 — 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) stream/stage_merge_sequence.go:116— stream/stage_merge_sequence.go:116-127 | stream/stage_zipn.go:88-99 — 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) actor/actor_system.go:4132— actor/actor_system.go:4132-4144 | actor/grain_pid.go:910-922 — 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) actor/grain_engine.go:1107— actor/grain_engine.go:1107-1121 | actor/grain_engine.go:1146-1158 — 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) actor/remote_server.go:658— actor/remote_server.go:658-670 | actor/remote_server.go:761-773 — 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) actor/remote_server.go:1260— actor/remote_server.go:1260-1272 | actor/remote_server.go:1325-1337 — 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) actor/spawn.go:116— actor/spawn.go:116-128 | actor/spawn.go:951-964 — 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/net/proto_serializer.go:187— internal/net/proto_serializer.go:187-199 | internal/net/proto_serializer.go:317-329 — 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) playground/issue-906/main.go:87— playground/issue-906/main.go:87-99 | playground/issue-908/main.go:78-90 — 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 × 2) stream/stage_merge_select.go:88— stream/stage_merge_select.go:88-100 | stream/stage_source.go:471-483 — 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) actor/bounded_stable_priority_mailbox.go:95— actor/bounded_stable_priority_mailbox.go:95-108 | actor/unbounded_stable_priority_mailbox.go:172-185 — 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) actor/grain_engine.go:996— actor/grain_engine.go:996-1009 | actor/pid.go:1328-1341 — 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) actor/remote_server.go:713— actor/remote_server.go:713-726 | actor/remote_server.go:1079-1092 — 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) client/client.go:415— client/client.go:415-428 | client/client.go:486-499 — 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) remote/spawn_request.go:193— remote/spawn_request.go:193-206 | remote/spawn_request.go:313-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 (14 lines × 2) stream/graph_builder.go:334— stream/graph_builder.go:334-347 | stream/graph_builder.go:356-369 — 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) actor/remote_server.go:676— actor/remote_server.go:676-687 | actor/spawn.go:1102-1112 — 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 × 2) actor/remote_server.go:1050— actor/remote_server.go:1050-1060 | actor/remote_server.go:1103-1114 — 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) discovery/consul/discovery.go:171— discovery/consul/discovery.go:171-181 | discovery/etcd/discovery.go:180-190 — 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) discovery/dnssd/discovery.go:117— discovery/dnssd/discovery.go:117-127 | discovery/nats/discovery.go:243-253 — 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/net/metadata.go:154— internal/net/metadata.go:154-164 | internal/net/metadata.go:166-176 — 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) stream/stage_flow.go:166— stream/stage_flow.go:166-176 | stream/stage_parallel.go:201-211 — 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) actor/scheduler.go:196— actor/scheduler.go:196-210 | actor/scheduler.go:239-253 — 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/chain/chain.go:88— internal/chain/chain.go:88-102 | internal/chain/chain.go:111-125 — 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/remoteclient/client.go:1914— internal/remoteclient/client.go:1914-1928 | internal/remoteclient/client.go:2177-2191 — 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) playground/issue-1203/main.go:125— playground/issue-1203/main.go:125-139 | playground/issue-1227/main.go:108-122 — 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) stream/stage_broadcast.go:278— stream/stage_broadcast.go:278-292 | stream/stage_partition.go:271-285 — 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 (12 lines × 3) actor/actor_system.go:4240— actor/actor_system.go:4240-4251 | actor/actor_system.go:4267-4278 | actor/actor_system.go:4294-4305 — 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 × 3) actor/remote_server.go:489— actor/remote_server.go:489-500 | actor/remote_server.go:537-548 | actor/remote_server.go:1220-1231 — 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 × 3) playground/issue-1017/main.go:111— playground/issue-1017/main.go:111-122 | playground/issue-973/main.go:83-94 | playground/issue-x/main.go:118-129 — 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 × 3) remote/grain_request.go:92— remote/grain_request.go:92-103 | remote/spawn_request.go:193-204 | remote/spawn_request.go:313-324 — 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 (12 lines × 3) stream/stage_balance.go:192— stream/stage_balance.go:192-203 | stream/stage_broadcast.go:197-210 | stream/stage_partition.go:193-204 — 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 (16 lines × 2) internal/remoteclient/client.go:1048— internal/remoteclient/client.go:1048-1063 | internal/remoteclient/client.go:1245-1260 — 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 × 2) internal/remoteclient/client.go:1300— internal/remoteclient/client.go:1300-1315 | internal/remoteclient/client.go:2107-2123 — 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 × 2) internal/remoteclient/client.go:1867— internal/remoteclient/client.go:1867-1882 | internal/remoteclient/client.go:2041-2056 — 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 × 2) remote/option.go:244— remote/option.go:244-259 | remote/option.go:296-311 — 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) actor/relocation_worker.go:712— actor/relocation_worker.go:712-721 | actor/remote_server.go:630-639 — 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) remote/cbor_serializer.go:244— remote/cbor_serializer.go:244-254 | remote/json_serializer.go:157-166 — 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) remote/config.go:90— remote/config.go:90-99 | remote/config.go:117-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 (10 lines × 2) stream/source.go:473— stream/source.go:473-482 | stream/source.go:502-511 — 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) actor/remote_server.go:1297— actor/remote_server.go:1297-1305 | actor/remote_server.go:1356-1364 — 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) actor/topic_actor.go:204— actor/topic_actor.go:204-213 | actor/topic_actor.go:474-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 (9 lines × 2) stream/flow.go:239— stream/flow.go:239-249 | stream/flow.go:335-343 — 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) stream/stage_flow.go:506— stream/stage_flow.go:506-514 | stream/stage_subflow.go:101-109 — 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 (8 lines × 2) actor/remote_server.go:451— actor/remote_server.go:451-458 | actor/remote_server.go:1237-1245 — 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) actor/root_guardian.go:54— actor/root_guardian.go:54-61 | actor/user_guardian.go:53-60 — 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 (8 lines × 2) playground/issue-973/main.go:143— playground/issue-973/main.go:143-150 | playground/issue-x/main.go:176-183 — 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) stream/flow.go:159— stream/flow.go:159-166 | stream/flow.go:428-435 — 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.
Medium IaC: KSV-0001 playground/issue-1260/deploy/k8s.yaml— Can elevate its own privileges
Medium IaC: KSV-0012 playground/issue-1260/deploy/k8s.yaml— Runs as root user One securityContext edit clears this facet's near-duplicate rules together: KSV-0012, KSV-0020, KSV-0021.
Medium IaC: KSV-0104 playground/issue-1260/deploy/k8s.yaml— Seccomp policies disabled One securityContext edit clears this facet's near-duplicate rules together: KSV-0030, KSV-0104.
Duplicated block (18 lines × 2) actor/pid.go:1058— actor/pid.go:1058-1075 | actor/pid.go:2817-2834 — 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 (18 lines × 2) actor/pid.go:1659— actor/pid.go:1659-1676 | actor/pid.go:1716-1733 — 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 (18 lines × 2) internal/remoteclient/client.go:2227— internal/remoteclient/client.go:2227-2244 | internal/remoteclient/client.go:2328-2345 — 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) actor/grain_context.go:855— actor/grain_context.go:855-870 | actor/pid.go:1058-1075 | actor/pid.go:2817-2834 — 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 (16 lines × 3) actor/pid_tree.go:493— actor/pid_tree.go:493-508 | actor/pid_tree.go:638-654 | actor/pid_tree.go:667-683 — 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) stream/stage_balance.go:132— stream/stage_balance.go:132-147 | stream/stage_broadcast.go:140-155 | stream/stage_partition.go:132-147 — 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: actor_system.go ↔ defaults.go actor/actor_system.go— `actor/actor_system.go` and `actor/defaults.go` change together 58% of the time (7 of the 12 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. They already sit in the same directory, so if they share structure, extract the common part into one unit; otherwise break the coupling.
Change coupling: actor_system.go ↔ stash.go actor/actor_system.go— `actor/actor_system.go` and `actor/stash.go` change together 53% of the time (16 of the 30 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. They already sit in the same directory, so if they share structure, extract the common part into one unit; otherwise break the coupling.
Duplicated block (17 lines × 2) actor/actor_system.go:2252— actor/actor_system.go:2252-2268 | actor/api.go:59-75 — 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 (17 lines × 2) actor/grain_engine.go:865— actor/grain_engine.go:865-881 | actor/grain_engine.go:985-1001 — 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 × 7) actor/remote_server.go:179— actor/remote_server.go:179-192 | actor/remote_server.go:332-345 | actor/remote_server.go:369-382 | actor/remote_server.go:427-440 | actor/remote_server.go:581-594 | actor/remote_server.go:1072-1085 | actor/remote_server.go:1392-1405 — 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 × 7) actor/remote_server.go:815— actor/remote_server.go:815-828 | actor/remote_server.go:903-916 | actor/remote_server.go:948-961 | actor/remote_server.go:988-1001 | actor/remote_server.go:1028-1041 | actor/remote_server.go:1140-1153 | actor/remote_server.go:1180-1193 — 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 × 3) playground/issue-1017/main.go:140— playground/issue-1017/main.go:140-153 | playground/issue-973/main.go:113-126 | playground/issue-x/main.go:147-160 — 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 (14 lines × 3) stream/stage_balance.go:230— stream/stage_balance.go:230-243 | stream/stage_broadcast.go:228-241 | stream/stage_partition.go:221-234 — 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 × 5) stream/source.go:209— stream/source.go:209-219 | stream/source.go:232-241 | stream/source.go:362-371 | stream/source.go:386-395 | stream/source.go:425-434 — 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 × 5) stream/stage_concat.go:72— stream/stage_concat.go:72-81 | stream/stage_merge_select.go:73-82 | stream/stage_merge_sequence.go:102-111 | stream/stage_source.go:457-467 | stream/stage_zipn.go:73-82 — 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 × 2) testkit/multi_nodes.go:164— testkit/multi_nodes.go:164-169 | testkit/multi_nodes.go:198-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 (6 lines × 2) testkit/testkit.go:120— testkit/testkit.go:120-125 | testkit/testnode.go:126-131 — 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 (5 lines × 2) testkit/grain_probe.go:265— testkit/grain_probe.go:265-270 | testkit/probe.go:485-489 — 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 (5 lines × 2) testkit/testkit.go:87— testkit/testkit.go:87-92 | testkit/testnode.go:71-75 — 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.
actorSystem.remoteSpawnHandler (cyclomatic 23) actor/remote_server.go:580— actorSystem.remoteSpawnHandler 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.
flowActor.Receive (cyclomatic 22) stream/stage_flow.go:74— flowActor.Receive 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.
ProtoServer.handleConn (cyclomatic 21) internal/net/proto_server.go:427— ProtoServer.handleConn 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.
parallelMapActor.Receive (cyclomatic 21) stream/stage_parallel.go:101— parallelMapActor.Receive 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.
actorSystem.remoteSpawnChildHandler (cyclomatic 20) actor/remote_server.go:707— actorSystem.remoteSpawnChildHandler 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.
PID.DiscoverActor (cyclomatic 20) actor/pid.go:1267— PID.DiscoverActor 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.
WorkerPool.cleanup (cyclomatic 20) internal/net/worker_pool.go:264— WorkerPool.cleanup 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.
actorSystem.activateGrainLocally (cyclomatic 19) actor/grain_engine.go:448— actorSystem.activateGrainLocally 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.
actorSystem.askGrainAcrossDataCenters (cyclomatic 19) actor/grain_engine.go:930— actorSystem.askGrainAcrossDataCenters 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.
actorSystem.recreateGrainOnce (cyclomatic 19) actor/grain_engine.go:1422— actorSystem.recreateGrainOnce 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.
PID.deliverAcrossHandoff (cyclomatic 19) actor/relocation_handoff.go:178— PID.deliverAcrossHandoff 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.
tree.deleteNode (cyclomatic 19) actor/pid_tree.go:336— tree.deleteNode 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.
replicatorActor.handleDataCenterAntiEntropy (cyclomatic 19) actor/replicator.go:1333— replicatorActor.handleDataCenterAntiEntropy 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.
sourceRefEndpointActor.Receive (cyclomatic 19) stream/stage_source_ref.go:99— sourceRefEndpointActor.Receive 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.
actor.restartSubtree (cyclomatic 18) actor/pid.go:3541— actor.restartSubtree 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.
actorSystem.deriveRelocationSetFromRegistry (cyclomatic 18) actor/actor_system.go:3430— actorSystem.deriveRelocationSetFromRegistry 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.
actorSystem.configPID (cyclomatic 18) actor/actor_system.go:3704— actorSystem.configPID 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.
actorSystem.tellGrainAcrossDataCenters (cyclomatic 18) actor/grain_engine.go:815— actorSystem.tellGrainAcrossDataCenters 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.
router.tailChopping (cyclomatic 18) actor/router.go:493— router.tailChopping 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.
ControlPlane.Register (cyclomatic 18) datacenter/controlplane/nats/control_plane.go:146— ControlPlane.Register 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.
balanceHubActor.Receive (cyclomatic 18) stream/stage_balance.go:188— balanceHubActor.Receive 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.
actorSystem.cleanupStaleLocalActors (cyclomatic 17) actor/actor_system.go:2716— actorSystem.cleanupStaleLocalActors 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.
actorSystem.persistPeerStateToPeers (cyclomatic 17) actor/actor_system.go:4537— actorSystem.persistPeerStateToPeers 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.
partitionHubActor.Receive (cyclomatic 17) stream/stage_partition.go:189— partitionHubActor.Receive 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.
subFlowSourceActor.routeElement (cyclomatic 17) stream/stage_subflow.go:408— subFlowSourceActor.routeElement 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.
actorSystem.runShutdownHooks (cyclomatic 16) actor/actor_system.go:4115— actorSystem.runShutdownHooks 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.
actorSystem.remoteAskHandler (cyclomatic 16) actor/remote_server.go:234— actorSystem.remoteAskHandler 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.
actorSystem.startRemoteServer (cyclomatic 16) actor/remote_server.go:1618— actorSystem.startRemoteServer 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.
replicatorActor.handlePostStart (cyclomatic 16) actor/replicator.go:236— replicatorActor.handlePostStart 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.
log.appendJSONEscaped (cyclomatic 16) log/slog.go:140— log.appendJSONEscaped 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.
broadcastHubActor.Receive (cyclomatic 16) stream/stage_broadcast.go:193— broadcastHubActor.Receive 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.
sinkActor.Receive (cyclomatic 16) stream/stage_sink.go:62— sinkActor.Receive 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.
remoteSourceBridgeActor.Receive (cyclomatic 16) stream/stage_source_ref.go:307— remoteSourceBridgeActor.Receive 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.
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[1] | LineNumber: 0 | BytePositionInLine: 1200.
WorkerPool.cleanup (cognitive 64) internal/net/worker_pool.go:264— WorkerPool.cleanup has cognitive complexity 64 (threshold 15). Drivers by points: if/else 45, loops 17, match/switch 2 (nesting depth added 44). 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.
ProtoServer.handleConn (cognitive 43) internal/net/proto_server.go:427— ProtoServer.handleConn has cognitive complexity 43 (threshold 15). Drivers by points: if/else 42, loops 1 (nesting depth added 22). 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.
flowActor.Receive (cognitive 42) stream/stage_flow.go:74— flowActor.Receive has cognitive complexity 42 (threshold 15). Drivers by points: if/else 32, loops 6, match/switch 4 (nesting depth added 28). 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.
remoteWatchRegistry.dropPID (cognitive 39) actor/remote_watch_registry.go:303— remoteWatchRegistry.dropPID has cognitive complexity 39 (threshold 15). Drivers by points: if/else 35, loops 4 (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.
parallelMapActor.Receive (cognitive 37) stream/stage_parallel.go:101— parallelMapActor.Receive has cognitive complexity 37 (threshold 15). Drivers by points: if/else 33, loops 2, boolean chains 1, match/switch 1 (nesting depth added 20). 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.
Controller.watchLoop (cognitive 35) internal/datacentercontroller/controller.go:402— Controller.watchLoop has cognitive complexity 35 (threshold 15). Drivers by points: if/else 26, match/switch 5, loops 3, jumps 1 (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.
sinkActor.Receive (cognitive 34) stream/stage_sink.go:62— sinkActor.Receive has cognitive complexity 34 (threshold 15). Drivers by points: if/else 26, loops 4, match/switch 4 (nesting depth added 24). 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.
actorSystem.recreateGrainOnce (cognitive 30) actor/grain_engine.go:1422— actorSystem.recreateGrainOnce has cognitive complexity 30 (threshold 15). Drivers by points: if/else 30 (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.
actorSystem.remoteSpawnHandler (cognitive 30) actor/remote_server.go:580— actorSystem.remoteSpawnHandler has cognitive complexity 30 (threshold 15). Drivers by points: if/else 30 (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.
tree.deleteNode (cognitive 30) actor/pid_tree.go:336— tree.deleteNode has cognitive complexity 30 (threshold 15). Drivers by points: if/else 20, loops 8, 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.
actorSystem.remoteAskHandler (cognitive 29) actor/remote_server.go:234— actorSystem.remoteAskHandler has cognitive complexity 29 (threshold 15). Drivers by points: if/else 28, loops 1 (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.
PID.DiscoverActor (cognitive 28) actor/pid.go:1267— PID.DiscoverActor has cognitive complexity 28 (threshold 15). Drivers by points: if/else 21, loops 5, 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.
router.tailChopping (cognitive 28) actor/router.go:493— router.tailChopping has cognitive complexity 28 (threshold 15). Drivers by points: if/else 22, boolean chains 3, match/switch 2, loops 1 (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.
ControlPlane.Register (cognitive 28) datacenter/controlplane/nats/control_plane.go:146— ControlPlane.Register has cognitive complexity 28 (threshold 15). Drivers by points: if/else 26, 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.
actorSystem.askGrainAcrossDataCenters (cognitive 27) actor/grain_engine.go:930— actorSystem.askGrainAcrossDataCenters has cognitive complexity 27 (threshold 15). Drivers by points: if/else 20, loops 5, 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.
remoteWatchRegistry.dropHost (cognitive 27) actor/remote_watch_registry.go:353— remoteWatchRegistry.dropHost has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17, loops 10 (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.
actorSystem.activateGrainLocally (cognitive 26) actor/grain_engine.go:448— actorSystem.activateGrainLocally has cognitive complexity 26 (threshold 15). Drivers by points: if/else 23, 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.
actorSystem.tellGrainAcrossDataCenters (cognitive 26) actor/grain_engine.go:815— actorSystem.tellGrainAcrossDataCenters has cognitive complexity 26 (threshold 15). Drivers by points: if/else 20, loops 5, 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.
PID.deliverAcrossHandoff (cognitive 26) actor/relocation_handoff.go:178— PID.deliverAcrossHandoff has cognitive complexity 26 (threshold 15). Drivers by points: if/else 19, boolean chains 4, 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.
balanceHubActor.Receive (cognitive 26) stream/stage_balance.go:188— balanceHubActor.Receive has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16, loops 8, boolean chains 1, match/switch 1 (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.
actorSystem.cleanupStaleLocalActors (cognitive 25) actor/actor_system.go:2716— actorSystem.cleanupStaleLocalActors has cognitive complexity 25 (threshold 15). Drivers by points: if/else 21, boolean chains 3, 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.
actorSystem.persistPeerStateToPeers (cognitive 25) actor/actor_system.go:4537— actorSystem.persistPeerStateToPeers has cognitive complexity 25 (threshold 15). Drivers by points: if/else 21, loops 2, 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.
actorSystem.deriveRelocationSetFromRegistry (cognitive 24) actor/actor_system.go:3430— actorSystem.deriveRelocationSetFromRegistry has cognitive complexity 24 (threshold 15). Drivers by points: if/else 21, 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.
topicActor.handleTopicMessage (cognitive 24) actor/topic_actor.go:435— topicActor.handleTopicMessage has cognitive complexity 24 (threshold 15). Drivers by points: if/else 19, loops 3, boolean chains 2 (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.
Client.SendBatchProto (cognitive 24) internal/net/client.go:408— Client.SendBatchProto has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16, match/switch 6, loops 2 (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.
log.appendJSONEscaped (cognitive 24) log/slog.go:140— log.appendJSONEscaped has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15, boolean chains 4, match/switch 4, 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.
chanSourceActor.Receive (cognitive 24) stream/stage_source.go:124— chanSourceActor.Receive has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11, loops 7, match/switch 5, jumps 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.
actorSystem.runShutdownHooks (cognitive 23) actor/actor_system.go:4115— actorSystem.runShutdownHooks has cognitive complexity 23 (threshold 15). Drivers by points: if/else 18, match/switch 4, 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.
broadcastHubActor.Receive (cognitive 23) stream/stage_broadcast.go:193— broadcastHubActor.Receive has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14, loops 8, 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.
actorSystem.remoteSpawnChildHandler (cognitive 22) actor/remote_server.go:707— actorSystem.remoteSpawnChildHandler has cognitive complexity 22 (threshold 15). Drivers by points: if/else 21, boolean chains 1 (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.
replicatorActor.handleDataCenterAntiEntropy (cognitive 22) actor/replicator.go:1333— replicatorActor.handleDataCenterAntiEntropy has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16, boolean chains 4, loops 2 (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.
sourceRefEndpointActor.Receive (cognitive 22) stream/stage_source_ref.go:99— sourceRefEndpointActor.Receive has cognitive complexity 22 (threshold 15). Drivers by points: if/else 17, boolean chains 4, 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.
ORSet.Merge (cognitive 21) crdt/or_set.go:130— ORSet.Merge has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, loops 8, 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.
ControlPlane.ListActive (cognitive 21) datacenter/controlplane/nats/control_plane.go:288— ControlPlane.ListActive has cognitive complexity 21 (threshold 15). Drivers by points: if/else 18, loops 2, 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.
stream.materializeWithHead (cognitive 21) stream/materializer.go:93— stream.materializeWithHead has cognitive complexity 21 (threshold 15). Drivers by points: if/else 19, loops 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.
partitionHubActor.Receive (cognitive 21) stream/stage_partition.go:189— partitionHubActor.Receive has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13, loops 6, boolean chains 1, match/switch 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.
subFlowSourceActor.routeElement (cognitive 21) stream/stage_subflow.go:408— subFlowSourceActor.routeElement has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16, boolean chains 3, match/switch 2 (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.
actor.restartSubtree (cognitive 20) actor/pid.go:3541— actor.restartSubtree has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13, loops 4, boolean chains 3 (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.
actorSystem.completeSpawn (cognitive 20) actor/actor_system.go:2522— actorSystem.completeSpawn has cognitive complexity 20 (threshold 15). Drivers by points: if/else 19, 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.
TCPServer.acceptLoop (cognitive 20) internal/net/tcp_server.go:400— TCPServer.acceptLoop has cognitive complexity 20 (threshold 15). Drivers by points: if/else 17, boolean chains 2, 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.
actorSystem.configPID (cognitive 19) actor/actor_system.go:3704— actorSystem.configPID has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17, loops 2 (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.
grainPID.deactivate (cognitive 19) actor/grain_pid.go:246— grainPID.deactivate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17, match/switch 2 (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.
PID.freeChildren (cognitive 19) actor/pid.go:2494— PID.freeChildren has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16, loops 2, 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.
replicatorActor.handlePostStart (cognitive 19) actor/replicator.go:236— replicatorActor.handlePostStart has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16, boolean chains 3 (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.
sinkRefEndpointActor.Receive (cognitive 19) stream/stage_sink_ref.go:73— sinkRefEndpointActor.Receive has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, 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.
remoteSourceBridgeActor.Receive (cognitive 19) stream/stage_source_ref.go:307— remoteSourceBridgeActor.Receive has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, 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.
actorSystem.validate (cognitive 18) actor/actor_system.go:2202— actorSystem.validate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 15, boolean chains 3 (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.
actorSystem.startRemoteServer (cognitive 18) actor/remote_server.go:1618— actorSystem.startRemoteServer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 16, boolean chains 1, 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.
ORSet.Delta (cognitive 18) crdt/or_set.go:187— ORSet.Delta has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, loops 6, 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.
memberlist.NewTransport (cognitive 18) internal/memberlist/transport.go:67— memberlist.NewTransport has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14, loops 2, match/switch 2 (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.
stream.applyFusion (cognitive 18) stream/materializer.go:205— stream.applyFusion has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, boolean chains 4, loops 3 (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.
actorSystem.deliverRemoteTellMessage (cognitive 17) actor/remote_server.go:1744— actorSystem.deliverRemoteTellMessage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17 (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.
deathWatch.handleTerminated (cognitive 17) actor/death_watch.go:77— deathWatch.handleTerminated has cognitive complexity 17 (threshold 15). Drivers by points: if/else 16, 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.
Graph.compile (cognitive 17) stream/graph_builder.go:191— Graph.compile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, loops 5 (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.
actor.allocateActors (cognitive 16) actor/relocation_worker.go:856— actor.allocateActors 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.
actorSystem.Spawn (cognitive 16) actor/spawn.go:87— actorSystem.Spawn has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 2 (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.
broadcast.start (cognitive 16) discovery/selfmanaged/broadcast.go:75— broadcast.start has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16 (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.
broadcast.recvLoop (cognitive 16) discovery/selfmanaged/broadcast.go:184— broadcast.recvLoop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, match/switch 2, boolean chains 1, 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.
Transport.FinalAdvertiseAddr (cognitive 16) internal/memberlist/transport.go:154— Transport.FinalAdvertiseAddr has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, match/switch 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.
client.RemoteTell (cognitive 16) internal/remoteclient/client.go:1676— client.RemoteTell has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, match/switch 2 (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.
client.RemoteBatchAsk (cognitive 16) internal/remoteclient/client.go:1998— client.RemoteBatchAsk has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, loops 2 (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.
stream.MergePrioritized (cognitive 16) stream/source.go:319— stream.MergePrioritized has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, loops 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.
remoteSinkBridgeActor.Receive (cognitive 16) stream/stage_sink_ref.go:195— remoteSinkBridgeActor.Receive has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 1, match/switch 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.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 40 floating ref(s) across 7 workflow file(s): `actions/checkout@v7` (.github/workflows/stale.yml:19), `actions/stale@v10` (.github/workflows/stale.yml:22), `github/codeql-action/upload-sarif@v3` (.github/workflows/scorecard.yml:72), `actions/checkout@v7` (.github/workflows/release.yml:30), `actions/checkout@v7` (.github/workflows/pr.yml:26), `dorny/paths-filter@v4` (.github/workflows/pr.yml:30), `actions/checkout@v7` (.github/workflows/pr.yml:56), `actions/setup-go@v6` (.github/workflows/pr.yml:61), … (+32 more)
D38 · OSV Dependency Vulnerabilities· Medium vulnerability · ×1
Medium vulnerability: GO-2026-5932 go.mod— golang.org/x/crypto 0.54.0 (golang.org/x/crypto/openpgp, golang.org/x/crypto/openpgp/packet, golang.org/x/crypto/openpgp/armor, +4 more): GO-2026-5932 — no fixed version has been published yet. Track the advisory, and remove or replace golang.org/x/crypto if the exposure is not acceptable until one lands.
Duplicated block (21 lines × 2) actor/grain_engine.go:942— actor/grain_engine.go:942-962 | actor/pid.go:1288-1308 — 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 (19 lines × 2) actor/grain_pid.go:600— actor/grain_pid.go:600-618 | actor/pid.go:2138-2156 — 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 (17 lines × 7) playground/issue-1017/main.go:222— playground/issue-1017/main.go:222-239 | playground/issue-1036/main.go:106-123 | playground/issue-1134/main.go:243-259 | playground/issue-1255/main.go:379-396 | playground/issue-791/main.go:180-197 | playground/issue-973/main.go:206-223 | playground/issue-x/main.go:209-226 — 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 × 3) playground/issue-1031/main.go:103— playground/issue-1031/main.go:103-120 | playground/issue-1203/main.go:142-158 | playground/issue-1227/main.go:125-141 — 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 × 5) internal/remoteclient/client.go:934— internal/remoteclient/client.go:934-949 | internal/remoteclient/client.go:991-1006 | internal/remoteclient/client.go:1096-1111 | internal/remoteclient/client.go:1144-1159 | internal/remoteclient/client.go:1197-1212 — 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) stream/stage_balance.go:76— stream/stage_balance.go:76-90 | stream/stage_broadcast.go:82-96 | stream/stage_partition.go:77-91 — 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 × 5) actor/pid_tree.go:456— actor/pid_tree.go:456-468 | actor/pid_tree.go:491-503 | actor/pid_tree.go:521-534 | actor/pid_tree.go:636-649 | actor/pid_tree.go:665-678 — 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) actor/bounded_priority_mailbox.go:88— actor/bounded_priority_mailbox.go:88-100 | actor/bounded_stable_priority_mailbox.go:82-94 | actor/unbounded_stable_priority_mailbox.go:159-171 — 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 (12 lines × 4) client/client.go:237— client/client.go:237-248 | client/client.go:273-284 | client/client.go:413-424 | client/client.go:484-495 — 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 × 3) stream/stage_concat.go:127— stream/stage_concat.go:127-137 | stream/stage_source.go:194-204 | stream/stage_source.go:502-512 — 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 × 4) stream/sink.go:140— stream/sink.go:140-149 | stream/sink.go:225-234 | stream/sink.go:246-255 | stream/sink.go:300-309 — 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.
Low IaC: KSV-0003 playground/issue-1260/deploy/k8s.yaml— Default capabilities: some containers do not drop all One securityContext edit clears this facet's near-duplicate rules together: KSV-0003, KSV-0004, KSV-0106.
Low IaC: KSV-0110 playground/issue-1260/deploy/k8s.yaml— Workloads in the default namespace
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.go) 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 133 significant file(s) lose their only recent owner: actor/actor_system.go, actor/pid.go, internal/remoteclient/client.go, actor/grain_engine.go, actor/spawn.go, actor/replicator.go, actor/grain_pid.go, actor/grain_context.go (+125 more). Pair on, review, or document these before any departure.
No artifact signing — No artifact signing found in CI — sign your released artifacts with whatever your ecosystem ships (a GPG/minisign detached signature — or `cosign sign-blob` — over the release archives, or over a checksum file published alongside them) so consumers can verify what you built.
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.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No seccomp profile — Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No AppArmor/SELinux confinement — Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
Coverage not included — suite not readable by the collector — Coverage NOT READ here — but this repository measures it: a Codecov configuration (codecov.yml, target 85%) and a coverage step in CI (`codecov/codecov-action`) show(s) coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.go), 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 ./...`) 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.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
0
—
Run 019fafcd-9944-75f0-8c27-3ec75105ab45 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 3 · Warnings: 215 · Recommendations: 11 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 29-07-2026 @ 21:35 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.