Public report of carverauto/threadr, published 22 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 22 October 2026, 17:01 UTC · Survey ID cd_944ee57b23654039b3c3ab74d7b47b40
carverauto/threadr
Measured 22 October 2026, 16:54 UTC, at code version aba5b16
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAt riskDown 5 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 35,192 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Security and Compliance, 39
Findings by how serious they are
86 critical939 serious388 minor
14 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 16:54 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
74of 78 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
1374of 1413 findings point to an exact file and line, so you can open each one in the code. The other 39 concern the repository as a whole, such as missing documentation.
78dimensions across 7 lenses, read from 35,192 lines of product code in 6 projects.
carverauto/threadr scores 43 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.
The weakest lens counts most in the score, and here that is Security and Compliance, which scores 39 and is rated Weak. Its Secrets (history) dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 6 Leaked secret finding(s) in REDACTED Scanning and to resolve the 1 No ADRs found finding(s) in ADR Quality. The weakest lenses score close to each other, so improving any of them moves the score.
86 findings are critical: 39 in IaC & Container Security, 20 in Dependency Vulnerabilities, ten in Secrets (history), ten in Static Analysis (SAST), six in REDACTED Scanning and one in Page structure.
Watchdog couldn't measure 10 dimensions in this code, among them Code Coverage, Test Reliability and Internal API Consistency, so they are left out of the score. The product code is 35,192 lines, which would take an estimated 0.3 person-years, around €43,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Large Files · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js: 736 lines of code elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js
Large Files · elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js: 632 lines of code elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js
Data Protection · No data-protection/encryption elixir/threadr/lib/threadr/control_plane/user.ex
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 3 findings
These 3 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one.
Dependency Vulnerabilities · Medium CVE: GO-2026-5841 REDACTED
IaC & Container Security · Medium IaC: CKV_K8S_19 REDACTED
Large Files · Large Files
Rebuild cost: about €43,000 · Estimate
Cost to rebuild
€14,000 to €72,000, for 238 to 755 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 43. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 35,192 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED.
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 2 points · Low effort · ADR Quality
3
Encrypt sensitive data at rest (Cloak.Ecto — a Cloak.Ecto.Binary-backed field type for the column — or ash_cloak for Ash) and manage keys in a vault (AWS KMS / Secrets Manager through ex_aws_kms, GCP KMS / REDACTED Manager, Azure Key Vault, HashiCorp Vault).
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 3 points · Medium effort · Data Protection
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €43,000 to build again, about 0.3 person-years of work. Its weakest lens is Security and Compliance, at 39 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 6 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
67 modules, with 22 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 27 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
1 pair of types, where a type in ThreadrWeb.ApiKeyLive uses a type in (global).
The types involved
ThreadrWeb.ApiKeyLive.Index → ThreadrWeb
Direction
ThreadrWeb.ApiKeyLive uses (global), so a change to (global) can break ThreadrWeb.ApiKeyLive, while a change to ThreadrWeb.ApiKeyLive can't break (global).
Position
Below the diagonal: ThreadrWeb.ApiKeyLive uses a module listed above it, which is the healthy direction.
ThreadrWeb.PasswordSettingsLive uses (global), so a change to (global) can break ThreadrWeb.PasswordSettingsLive, while a change to ThreadrWeb.PasswordSettingsLive can't break (global).
Position
Below the diagonal: ThreadrWeb.PasswordSettingsLive uses a module listed above it, which is the healthy direction.
ThreadrWeb.SystemLlmSettingsLive uses (global), so a change to (global) can break ThreadrWeb.SystemLlmSettingsLive, while a change to ThreadrWeb.SystemLlmSettingsLive can't break (global).
Position
Below the diagonal: ThreadrWeb.SystemLlmSettingsLive uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in ThreadrWeb.TenantBotLive uses a type in (global).
The types involved
ThreadrWeb.TenantBotLive.Index → ThreadrWeb
Direction
ThreadrWeb.TenantBotLive uses (global), so a change to (global) can break ThreadrWeb.TenantBotLive, while a change to ThreadrWeb.TenantBotLive can't break (global).
Position
Below the diagonal: ThreadrWeb.TenantBotLive uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in ThreadrWeb.TenantDossierLive uses a type in (global).
The types involved
ThreadrWeb.TenantDossierLive.Show → ThreadrWeb
Direction
ThreadrWeb.TenantDossierLive uses (global), so a change to (global) can break ThreadrWeb.TenantDossierLive, while a change to ThreadrWeb.TenantDossierLive can't break (global).
Position
Below the diagonal: ThreadrWeb.TenantDossierLive uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in ThreadrWeb.TenantGraphLive uses a type in (global).
The types involved
ThreadrWeb.TenantGraphLive.Index → ThreadrWeb
Direction
ThreadrWeb.TenantGraphLive uses (global), so a change to (global) can break ThreadrWeb.TenantGraphLive, while a change to ThreadrWeb.TenantGraphLive can't break (global).
Position
Below the diagonal: ThreadrWeb.TenantGraphLive uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in ThreadrWeb.TenantHistoryLive uses a type in (global).
The types involved
ThreadrWeb.TenantHistoryLive.Index → ThreadrWeb
Direction
ThreadrWeb.TenantHistoryLive uses (global), so a change to (global) can break ThreadrWeb.TenantHistoryLive, while a change to ThreadrWeb.TenantHistoryLive can't break (global).
Position
Below the diagonal: ThreadrWeb.TenantHistoryLive uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in ThreadrWeb.TenantLive uses a type in (global).
The types involved
ThreadrWeb.TenantLive.Index → ThreadrWeb
Direction
ThreadrWeb.TenantLive uses (global), so a change to (global) can break ThreadrWeb.TenantLive, while a change to ThreadrWeb.TenantLive can't break (global).
Position
Below the diagonal: ThreadrWeb.TenantLive uses a module listed above it, which is the healthy direction.
ThreadrWeb.TenantLlmSettingsLive uses (global), so a change to (global) can break ThreadrWeb.TenantLlmSettingsLive, while a change to ThreadrWeb.TenantLlmSettingsLive can't break (global).
Position
Below the diagonal: ThreadrWeb.TenantLlmSettingsLive uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in ThreadrWeb.TenantQaLive uses a type in (global).
The types involved
ThreadrWeb.TenantQaLive.Index → ThreadrWeb
Direction
ThreadrWeb.TenantQaLive uses (global), so a change to (global) can break ThreadrWeb.TenantQaLive, while a change to ThreadrWeb.TenantQaLive can't break (global).
Position
Below the diagonal: ThreadrWeb.TenantQaLive uses a module listed above it, which is the healthy direction.
github.com/carverauto/threadr/cmd/bots/discord uses github.com/carverauto/threadr/pkg/adapters/broker, so a change to github.com/carverauto/threadr/pkg/adapters/broker can break github.com/carverauto/threadr/cmd/bots/discord, while a change to github.com/carverauto/threadr/cmd/bots/discord can't break github.com/carverauto/threadr/pkg/adapters/broker.
Position
Below the diagonal: github.com/carverauto/threadr/cmd/bots/discord uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane uses a type in github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1.
github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane uses github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1, so a change to github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1 can break github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane, while a change to github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane can't break github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1.
Position
Below the diagonal: github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/carverauto/threadr/pkg/adapters/cloudevents uses a type in github.com/carverauto/threadr/pkg/adapters/broker.
github.com/carverauto/threadr/pkg/adapters/cloudevents uses github.com/carverauto/threadr/pkg/adapters/broker, so a change to github.com/carverauto/threadr/pkg/adapters/broker can break github.com/carverauto/threadr/pkg/adapters/cloudevents, while a change to github.com/carverauto/threadr/pkg/adapters/cloudevents can't break github.com/carverauto/threadr/pkg/adapters/broker.
Position
Below the diagonal: github.com/carverauto/threadr/pkg/adapters/cloudevents uses a module listed above it, which is the healthy direction.
github.com/carverauto/threadr/pkg/ports uses github.com/carverauto/threadr/pkg/adapters/broker, so a change to github.com/carverauto/threadr/pkg/adapters/broker can break github.com/carverauto/threadr/pkg/ports, while a change to github.com/carverauto/threadr/pkg/ports can't break github.com/carverauto/threadr/pkg/adapters/broker.
Position
Below the diagonal: github.com/carverauto/threadr/pkg/ports uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/carverauto/threadr/k8s/operator/ircbot-operator/cmd/threadrbot-smoke uses a type in github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1.
github.com/carverauto/threadr/k8s/operator/ircbot-operator/cmd/threadrbot-smoke uses github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1, so a change to github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1 can break github.com/carverauto/threadr/k8s/operator/ircbot-operator/cmd/threadrbot-smoke, while a change to github.com/carverauto/threadr/k8s/operator/ircbot-operator/cmd/threadrbot-smoke can't break github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1.
Position
Below the diagonal: github.com/carverauto/threadr/k8s/operator/ircbot-operator/cmd/threadrbot-smoke uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/carverauto/threadr/k8s/operator/ircbot-operator/cmd/threadrbot-smoke uses a type in github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane.
github.com/carverauto/threadr/k8s/operator/ircbot-operator/cmd/threadrbot-smoke uses github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane, so a change to github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane can break github.com/carverauto/threadr/k8s/operator/ircbot-operator/cmd/threadrbot-smoke, while a change to github.com/carverauto/threadr/k8s/operator/ircbot-operator/cmd/threadrbot-smoke can't break github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane.
Position
Below the diagonal: github.com/carverauto/threadr/k8s/operator/ircbot-operator/cmd/threadrbot-smoke uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controller uses a type in github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1.
github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controller uses github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1, so a change to github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1 can break github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controller, while a change to github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controller can't break github.com/carverauto/threadr/k8s/operator/ircbot-operator/api/v1alpha1.
Position
Below the diagonal: github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controller uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controller uses a type in github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane.
github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controller uses github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane, so a change to github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane can break github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controller, while a change to github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controller can't break github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controlplane.
Position
Below the diagonal: github.com/carverauto/threadr/k8s/operator/ircbot-operator/internal/controller uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/carverauto/threadr/pkg/adapters/messages uses a type in github.com/carverauto/threadr/pkg/adapters/broker.
github.com/carverauto/threadr/pkg/adapters/messages uses github.com/carverauto/threadr/pkg/adapters/broker, so a change to github.com/carverauto/threadr/pkg/adapters/broker can break github.com/carverauto/threadr/pkg/adapters/messages, while a change to github.com/carverauto/threadr/pkg/adapters/messages can't break github.com/carverauto/threadr/pkg/adapters/broker.
Position
Below the diagonal: github.com/carverauto/threadr/pkg/adapters/messages uses a module listed above it, which is the healthy direction.
github.com/carverauto/threadr/pkg/adapters/messages uses github.com/carverauto/threadr/pkg/ports, so a change to github.com/carverauto/threadr/pkg/ports can break github.com/carverauto/threadr/pkg/adapters/messages, while a change to github.com/carverauto/threadr/pkg/adapters/messages can't break github.com/carverauto/threadr/pkg/ports.
Position
Below the diagonal: github.com/carverauto/threadr/pkg/adapters/messages uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 39% · Weak · gated by R1, R2, R3 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A02:2025 — Security Misconfiguration
877
High / Critical
A03:2025 — Software Supply Chain Failures
42
High / Critical
A05:2025 — Injection
37
High / Critical
A07:2025 — Authentication Failures
17
High / Critical
Roadmap
Immediately secure sensitive data by implementing column-level encryption and managing keys in a dedicated vault, while simultaneously resolving all leaked secrets in configuration and test files. Address the 116 orphaned files in the knowledge base, prioritizing index and main source files, and establish architectural decision records to document key system choices. Finally, improve frontend reliability by adopting TypeScript, starting with a typecheck step in the build process and converting the highest-traffic modules first.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED.
Encrypt sensitive data at rest (Cloak.Ecto — a Cloak.Ecto.Binary-backed field type for the column — or ash_cloak for Ash) and manage keys in a vault (AWS KMS / Secrets Manager through ex_aws_kms, GCP KMS / REDACTED Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Reconcile the README with reality: README.md links to `/Users/mfreeman/src/threadr/elixir/threadr`, but `Users/mfreeman/src/threadr/elixir/threadr` does not exist; README.md links to `/Users/mfreeman/src/threadr/k8s/threadr`, but `Users/mfreeman/src/threadr/k8s/threadr` does not exist; README.md links to `/Users/mfreeman/src/threadr/openspec`, but `Users/mfreeman/src/threadr/openspec` does not exist; README.md links to `/Users/mfreeman/src/threadr/cmd`, but `Users/mfreeman/src/threadr/cmd` does not exist; README.md links to `/Users/mfreeman/src/threadr/elixir/threadr/README.md`, but `Users/mfreeman/src/threadr/elixir/threadr/README.md` does not exist.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 86
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 939
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 388
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 14
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
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. 74 of 78 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — 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 — 78 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, 1374 of 1413 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.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.exs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `mix test --cover` with `excoveralls` (`mix coveralls.lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `mix test --cover` with `excoveralls` (`mix coveralls.lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.exs) 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.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 486 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. K8s/operators/ircbot-operator/bundle/manifests/ircbot-operator.clusterserviceversion.yaml:2, REDACTED:2 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — cnpg Pulling nats Pulling nats Error Get "https://registry-1.docker.io/v2/": Forbidden cnpg Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: nats Pulling cnpg Pulling nats Error Get "https://registry-1.docker.io/v2/": Forbidden cnpg Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Elixir, Go, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Elixir, Go, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. X7 measured the part of this repository it reads (C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart), and its Elixir source is outside the check's reach, so the card covers only part of the product. That is a gap in this analyzer's language reach — not a finding that the unread source is free of silent defaults.
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 — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
The LLM boundary
LLM-set scores this run (4): D19, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They 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.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 12 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with updateSelectionDetails (cyclomatic 26), tooltipText (cyclomatic 25), nodeLabel (cyclomatic 22). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 12 together lifts Cyclomatic Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 16 bodies over 15 down to 15 or less in Cognitive Complexity — start with decodeArrowGraph (cognitive 24), edgeColor (cognitive 23), IRCAdapter.Send (cognitive 22). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 16 together lifts Cognitive Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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 Classes7.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 13 FileTooLong finding(s) in God Classes — start with index.ex (3), service.ex, constrained_qa.ex. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 6 TooManyFunctions finding(s) in God Classes — start with hybrid_retriever.ex, conversation_summary_qa.ex, reconstruction_candidates.ex. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 FunctionTooLong finding(s) in God Classes — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
109 duplicated block group(s) detected. A further 8 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 51 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with consumer.ex (2), actor_qa.ex, membership_controller.ex. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 8 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with threadr.generation.answer.ex, conversation_qa.ex, graph_inspector.ex. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with service.ex (2), threadr.smoke.discord_message.ex, smoke_server.ex. — One of this dimension's main actionable groups (7 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
6 production modules (Cargo+npm+Go+OTP), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 3 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
D9 · Test Distribution8.9 / 10Strong✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
12 test methods: 11 unit, 0 integration, 0 BDD, 1 e2e. The Go suite contributes 12 test case(s) across 5 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
What to do
Improve Test Distribution — currently 8.9/10. — 12 test methods: 11 unit, 0 integration, 0 BDD, 1 e2e. The Go suite contributes 12 test case(s) across 5 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
21 outdated, 1 retired direct Hex dependencies, 1 pinning defect(s). Whether any of these packages is UNMAINTAINED is not graded — hex.pm publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: a Hex app name does not determine the modules it provides (`ecto_sql` provides Ecto.Adapters.SQL), and a large idiomatic class of BEAM dependencies — runtime adapters, codec plugins, protocol implementations and OTP applications the release starts — is correctly declared and never referenced in source, so absence of a reference is not evidence of an unused dependency. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Retired release: jetstream
Unbounded dependency requirement: postgrex
Outdated: ash · ×21
What to do
Resolve the 1 Retired release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unbounded dependency requirement finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 71 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's Cargo.lock closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
Top hotspots: elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js (3×26=78); elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js (3×17=51); elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js (3×15=45) Repeated repair below the complexity floor: elixir/threadr/lib/threadr/ingest/bot_qa.ex (7 of 9 changes were fixes); elixir/threadr/lib/threadr/ml/conversation_qa.ex (3 of 3 changes were fixes)
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with rendering_selection_methods.js, ThreadrGraphRenderer.js, rendering_graph_methods.js. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with bot_qa.ex, conversation_qa.ex. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
4 deducted task-comment markers across 35192 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 4 TodoComment finding(s) in Explicit Debt — start with ircbot_controller_test.go (3), batch_processor.go. — One of this dimension's main actionable groups (4 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README is a clear overview of Threadr (an Elixir-based conversation intelligence system for tenant-scoped chat ingestion, reconstruction, QA, and bot runtimes) with an outline that includes What Threadr Does; Repository Layout; Getting Started; Verification; Community. The k8s directories each have their own focused READMEs covering setup, node prep, sysctl, IPv6 privacy, and specific tools like k3s, Calico CNI, linkerd, metallb, and the neo4j helm chart for Nebula studio. The elixir/threadr/README is a scaffold documenting what exists in the Phoenix/Broadway rewrite foundation (Phoenix LiveView app, Ash foundations, NATS JetStream topology, mix commands to provision initial streams, smoke tests), with an outline that includes Local Development; Runtime Configuration; Ingest Runtime; ML Boundaries; Multitenancy Shape. The cmd/natsctl/README and k8s/operators/ircbot-operator/README are focused on the natsctl CLI tool and its integration into the control-plane contract feed, respectively, each with a complete outline. All documents are clipped by the scanner at the end of their outlines, so unshown sections cannot be flagged as missing; the visible content is clear and well-structured.
What to do
Improve Documentation Quality — currently 8.0/10. — The repository's root README is a clear overview of Threadr (an Elixir-based conversation intelligence system for tenant-scoped chat ingestion, reconstruction, QA, and bot runtimes) with an outline that includes What Threadr Does; Repository Layout; Getting Started; Verification; Community. The k8s directories each have their own focused READMEs covering setup, node prep, sysctl, IPv6 privacy, and specific tools like k3s, Calico CNI, linkerd, metallb, and the neo4j helm chart for Nebula studio. The elixir/threadr/README is a scaffold documenting what exists in the Phoenix/Broadway rewrite foundation (Phoenix LiveView app, Ash foundations, NATS JetStream topology, mix commands to provision initial streams, smoke tests), with an outline that includes Local Development; Runtime Configuration; Ingest Runtime; ML Boundaries; Multitenancy Shape. The cmd/natsctl/README and k8s/operators/ircbot-operator/README are focused on the natsctl CLI tool and its integration into the control-plane contract feed, respectively, each with a complete outline. All documents are clipped by the scanner at the end of their outlines, so unshown sections cannot be flagged as missing; the visible content is clear and well-structured.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
10 finding(s): 0 critical, 10 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 10 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (10 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
37 finding(s): 0 critical, 10 high, 26 medium, 1 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `buildbuddy_setup_docker_auth.sh` (lines 2–58), `k8s/cert-manager/azure/issuer.yaml` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 20 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10), REDACTED (10). — One of this dimension's main actionable groups (20 warning-level).
Resolve the 15 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11), REDACTED (4). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 677 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (140), REDACTED (72), REDACTED (55). — One of this dimension's main actionable groups (677 warning-level).
Resolve the 33 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (33 issue-level).
Resolve the 6 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 issue-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.
119 of 119 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is elixir/threadr/lib/threadr/control_plane/service.ex. Counted over 119 of the 287 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3elixir/threadr/lib/threadr/control_plane/service.ex:1
Dormant codebase
What to do
Resolve the 116 Orphaned file finding(s) in Knowledge Freshness — start with index.ex (8), main.go (4), ingest.ex (2). — One of this dimension's main actionable groups (116 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with service.ex, index.ex, constrained_qa.ex. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
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.
7/35 workload(s) run every container under a seccomp profile; 0/35 declare an AppArmor/SELinux profile.
No seccomp profile · ×28REDACTED:2
What to do
Resolve the 28 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (4), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (28 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the Kubernetes deployment wires runtime threat enforcement — a detection engine (Tetragon/Falco) and/or an admission-control policy gate (Kyverno / OPA Gatekeeper / PodSecurity). Presence of committed policy, not a runtime guarantee.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a runtime threat-detection engine (Tetragon TracingPolicy / Falco) and an admission-control policy (Kyverno / OPA Gatekeeper / PodSecurity). Reward-leaning; NotApplicable without workloads. Deterministic.
Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No admission-control policy finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d42_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Do you agree with this assessment?
AC3 · Page structure4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — elixir/threadr/lib/threadr_web/components/layouts/root.html.heex:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — elixir/threadr/lib/threadr_web/components/layouts/root.html.heex:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
C1 · Data Protection0.0 / 10Critical✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No encryption usage (Cloak.Ecto encrypted field types, a Cloak vault, Plug.Crypto's message encryptor, :crypto ciphers that encrypt, libsodium boxes) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — elixir/threadr/lib/threadr/control_plane/user.ex:119
What to do
Encrypt sensitive data at rest (Cloak.Ecto — a Cloak.Ecto.Binary-backed field type for the column — or ash_cloak for Ash) and manage keys in a vault (AWS KMS / Secrets Manager through ex_aws_kms, GCP KMS / REDACTED Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
Enforce HTTPS (force_ssl: [hsts: true] on the Phoenix endpoint, or plug Plug.SSL, or an https: listener) so data in transit is always encrypted.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
Name the access rules — a Bodyguard.Policy or LetMe policy module, a Canada.Can implementation, or roles and permissions declared once — and consult them where access is checked (Bodyguard.permit!, a plug in the pipeline), so the rule set is reviewable and testable on its own.
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
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add a README to the 3 of 5 project(s) that lack one — worth up to 1.2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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.
README.md links to `/Users/mfreeman/src/threadr/elixir/threadr`, but `Users/mfreeman/src/threadr/elixir/threadr` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:19
README.md links to `/Users/mfreeman/src/threadr/k8s/threadr`, but `Users/mfreeman/src/threadr/k8s/threadr` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:43
README.md links to `/Users/mfreeman/src/threadr/openspec`, but `Users/mfreeman/src/threadr/openspec` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:44
README.md links to `/Users/mfreeman/src/threadr/cmd`, but `Users/mfreeman/src/threadr/cmd` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:45
README.md links to `/Users/mfreeman/src/threadr/elixir/threadr/README.md`, but `Users/mfreeman/src/threadr/elixir/threadr/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:51
elixir/threadr/README.md names `threadr/cnpg-app`, but no file or folder `threadr/cnpg-app` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:48
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/control-plane/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/control-plane/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:128
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/production/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/production/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:154
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/nginx-tls/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/nginx-tls/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:178
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/prometheus-servicemonitor/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/prometheus-servicemonitor/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:180
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/restricted-network/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/restricted-network/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:182
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/bot-operator/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/bot-operator/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:193
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/REDACTED#L1`, but `Users/mfreeman/src/threadr/REDACTED` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:222
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/ghcr/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/ghcr/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:224
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/REDACTED#L1`, but `Users/mfreeman/src/threadr/REDACTED` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:249
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/control-plane/application.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/control-plane/application.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:254
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/worker/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/worker/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:266
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/worker/production/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/worker/production/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:268
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/control-plane/seal_control_plane_env.sh#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/control-plane/seal_control_plane_env.sh` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:284
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/REDACTED#L1`, but `Users/mfreeman/src/threadr/REDACTED` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:331
elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/operators/ircbot-operator/config/crd/bases/cache.threadr.ai_threadrbots.yaml`, but `Users/mfreeman/src/threadr/k8s/operators/ircbot-operator/config/crd/bases/cache.threadr.ai_threadrbots.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — elixir/threadr/README.md:525
What to do
Reconcile the README with reality: README.md links to `/Users/mfreeman/src/threadr/elixir/threadr`, but `Users/mfreeman/src/threadr/elixir/threadr` does not exist; README.md links to `/Users/mfreeman/src/threadr/k8s/threadr`, but `Users/mfreeman/src/threadr/k8s/threadr` does not exist; README.md links to `/Users/mfreeman/src/threadr/openspec`, but `Users/mfreeman/src/threadr/openspec` does not exist; README.md links to `/Users/mfreeman/src/threadr/cmd`, but `Users/mfreeman/src/threadr/cmd` does not exist; README.md links to `/Users/mfreeman/src/threadr/elixir/threadr/README.md`, but `Users/mfreeman/src/threadr/elixir/threadr/README.md` does not exist.
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
Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
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.
What to do
The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`Req.post!(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — elixir/threadr/lib/mix/tasks/threadr.smoke.discord_message.ex:339
`http.Post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — pkg/adapters/messages/mistral7b_analyzer.go:49
What to do
Set an explicit timeout on every client — `recv_timeout:` for HTTPoison, `receive_timeout:` for Req and Finch, `Tesla.Middleware.Timeout` (or the adapter's `recv_timeout`) for Tesla, `timeout:` for `:httpc` — and add retries with back-off (`Tesla.Middleware.Retry`, Req's `retry:`) and a breaker (`:fuse`, `ExternalService`) around dependencies that fail.
Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 11 plain JS — the untyped files are elixir/threadr/assets/js/app.js, elixir/threadr/assets/js/hooks/index.js, elixir/threadr/assets/js/hooks/tenant_graph_explorer.js, elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js, elixir/threadr/assets/js/lib/threadr_graph/layout_cluster_methods.js, elixir/threadr/assets/js/lib/threadr_graph/lifecycle_stream_methods.js (+5 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:815 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:856 — 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. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:815
elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:490 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:711 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:490
elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:35 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:165 — 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. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:35
elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:225 · elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:182 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:225
elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:756 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:787 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:830 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:756
elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:738 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:770 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:844 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:738
elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:193 · elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:310 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:193
elixir/threadr/assets/js/lib/threadr_graph/layout_cluster_methods.js:51 · elixir/threadr/assets/js/lib/threadr_graph/layout_cluster_methods.js:81 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — elixir/threadr/assets/js/lib/threadr_graph/layout_cluster_methods.js:51
elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:115 · elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:124 — 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. — elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:115
elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:668 · elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:694 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:668
elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:520 · elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:532 — 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. — elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:520
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
updateSelectionDetails has cyclomatic complexity 26 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:18
tooltipText has cyclomatic complexity 25 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:515
nodeLabel has cyclomatic complexity 22 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:629
decodeArrowGraph has cyclomatic complexity 19 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/lifecycle_stream_methods.js:41
constructor has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:10
(anonymous) has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:625
renderNodeDossier has cyclomatic complexity 16 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:412
edgeColor has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:265
relationshipEdgePreserve has cyclomatic complexity 15 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:442
historyHref has cyclomatic complexity 15 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:539
clusterToNode has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/layout_cluster_methods.js:113
shouldShowNeighborhoodLabel has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:605
shouldShowNodeLabel has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:576
showMessagesForFocus has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:160
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files2.7 / 10Weak✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js has 736 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:1
elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js has 632 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling3.4 / 10Weak✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's Elixir source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (elixir/threadr/lib/threadr/control_plane/smoke_server.ex:63 — `Bandit`), so its Elixir source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Elixir spelling appears in production source, not proven on every route. A router that plugs Phoenix's `put_secure_browser_headers` is credited the headers Phoenix sends by default (`content-security-policy` from Phoenix 1.8, `x-frame-options` before it, as the `REDACTED` pins), and a cookie Plug sets the HttpOnly flag it sets by default.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
This repository runs an HTTP server and nothing in its Elixir source or production configuration secures the transport: no HTTPS served (an endpoint's `https: [...]`, `scheme: :https`, `Plug.Cowboy.https`, SiteEncrypt), no `force_ssl:` or `plug Plug.SSL` redirecting to HTTPS and sending HSTS, no `strict-transport-security` header, no `rewrite_on: [:x_forwarded_proto]` or `x-forwarded-proto` read for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: elixir/threadr/lib/threadr/control_plane/smoke_server.ex:63 — `Bandit`.
Set: Content-Security-Policy, Referrer-Policy, X-Content-Type-Options, X-Permitted-Cross-Domain-Policies. Missing: Strict-Transport-Security, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.0 on this card.) The server: elixir/threadr/lib/threadr/control_plane/smoke_server.ex:63 — `Bandit`.
What to do
Secure the server's transport: set `force_ssl: [rewrite_on: [:x_forwarded_proto], hsts: true]` on the endpoint in `config/prod.exs` (Plug.SSL redirects to HTTPS and sends `Strict-Transport-Security`; `rewrite_on` trusts the TLS-terminating proxy in front of it), or serve TLS itself with the endpoint's `https: [port: 443, cipher_suite: :strong, keyfile: …, certfile: …]`.
Add Strict-Transport-Security, X-Frame-Options beside the headers the Elixir server already sets.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether functions that make a cancellable request accept or pass on a context.Context or an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 3/7 functions that make a cancellable request (fetch, axios, ky, ofetch; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`AccessSecureEndpoint` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — cmd/client/admin/secure.go:11
`GetClaims` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — cmd/client/admin/claims.go:12
`SendClaimsUpdate` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — cmd/client/admin/claims.go:51
`init` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — elixir/threadr/assets/js/wasm/threadr_graph_exec_runtime.js:10
What to do
Thread a context.Context or an AbortSignal through functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped6.1 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`this.escapeAttribute(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:590
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or schema — a module, Ecto schema or migration table named for it — ExAudit, PaperTrail, AshPaperTrail or Carbonite recording each change, or a Commanded / EventStore event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 47 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 image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — Not applicable: the BEAM has no dependency-injection container — state lives in processes, and no process is handed an instance whose lifetime another one scopes; this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. Elixir processes share no mutable memory — state lives in a process's own mailbox — so there is no shared object to race on. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — cnpg Pulling nats Pulling nats Error Get "https://registry-1.docker.io/v2/": Forbidden cnpg Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: nats Pulling cnpg Pulling nats Error Get "https://registry-1.docker.io/v2/": Forbidden cnpg Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D10 Test Quality — ~14402 lines of test source are present (.exs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — 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 — no .exs test runner
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.ex), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 2 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit)
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 Go aggregate(s) recording domain events (own events-slice append / raise-record))
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `mix test --cover` with `excoveralls` (`mix coveralls.lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for Benchee jobs (the entries of a `Benchee.run` job map) or Benchfella `bench "…"` blocks under `use Benchfella` in any `.ex`/`.exs` file, or benchee or benchfella in a mix.exs, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Go code has 3,676 production line(s), 4 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — the JS/TS workspace (10 production file(s)) has no JavaScript/TypeScript test, but it is 5.61% of this repository's production source and the other 94.39% carries 14,402 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
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.
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> elixir/threadr/lib/threadr_web/components/layouts/root.html.heex:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
FileTooLong: control_plane/service.ex elixir/threadr/lib/threadr/control_plane/service.ex— FileTooLong — 1156 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 120 functions. The bar is 500 significant lines; this is 656 over it, 2.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ml/constrained_qa.ex elixir/threadr/lib/threadr/ml/constrained_qa.ex— FileTooLong — 957 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 68 functions. The bar is 500 significant lines; this is 457 over it, 1.91× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tenant_qa_live/index.ex elixir/threadr/lib/threadr_web/live/tenant_qa_live/index.ex— FileTooLong — 924 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 43 functions. The bar is 500 significant lines; this is 424 over it, 1.85× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tenant_data/ingest.ex elixir/threadr/lib/threadr/tenant_data/ingest.ex— FileTooLong — 834 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 37 functions. The bar is 500 significant lines; this is 334 over it, 1.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tenant_history_live/index.ex elixir/threadr/lib/threadr_web/live/tenant_history_live/index.ex— FileTooLong — 710 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 210 over it, 1.42× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tenant_dossier_live/show.ex elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex— FileTooLong — 689 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 32 functions. The bar is 500 significant lines; this is 189 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: discord/consumer.ex elixir/threadr/lib/threadr/ingest/discord/consumer.ex— FileTooLong — 670 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 55 functions. The bar is 500 significant lines; this is 170 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tenant_bot_live/index.ex elixir/threadr/lib/threadr_web/live/tenant_bot_live/index.ex— FileTooLong — 668 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 168 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tenant_data/graph_snapshot.ex elixir/threadr/lib/threadr/tenant_data/graph_snapshot.ex— FileTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 39 functions. The bar is 500 significant lines; this is 106 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ml/actor_qa.ex elixir/threadr/lib/threadr/ml/actor_qa.ex— FileTooLong — 590 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 51 functions. The bar is 500 significant lines; this is 90 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tenant_data/graph.ex elixir/threadr/lib/threadr/tenant_data/graph.ex— FileTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 38 functions. The bar is 500 significant lines; this is 79 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ingest/bot_qa.ex elixir/threadr/lib/threadr/ingest/bot_qa.ex— FileTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 48 functions. The bar is 500 significant lines; this is 42 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tenant_data/graph_inspector.ex elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex— FileTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 32 functions. The bar is 500 significant lines; this is 34 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (5 lines × 2) elixir/threadr/lib/threadr/ml/actor_qa.ex:580— elixir/threadr/lib/threadr/ml/actor_qa.ex:580-584 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:372-376 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/semantic_qa.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) elixir/threadr/lib/threadr_web/controllers/api/v1/membership_controller.ex:43— elixir/threadr/lib/threadr_web/controllers/api/v1/membership_controller.ex:43-47 | elixir/threadr/lib/threadr_web/controllers/api/v1/membership_controller.ex:56-60 — 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 (5 lines × 2) elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:235— elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:235-239 | elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex:303-307 — `elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex` and `elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 54 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) elixir/threadr/lib/threadr/control_plane/analysis.ex:459— elixir/threadr/lib/threadr/control_plane/analysis.ex:459-463 | elixir/threadr/lib/threadr/control_plane/service.ex:1032-1036 — before extracting anything, compare `elixir/threadr/lib/threadr/control_plane/analysis.ex` and `elixir/threadr/lib/threadr/control_plane/service.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) elixir/threadr/lib/threadr/control_plane/kubernetes_bot_reconciler.ex:139— elixir/threadr/lib/threadr/control_plane/kubernetes_bot_reconciler.ex:139-143 | elixir/threadr/lib/threadr/control_plane/service.ex:90-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) elixir/threadr/lib/threadr/ml/constrained_qa.ex:1000— elixir/threadr/lib/threadr/ml/constrained_qa.ex:1000-1004 | elixir/threadr/lib/threadr/ml/hybrid_retriever.ex:570-574 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) elixir/threadr/lib/threadr/control_plane/service.ex:1064— elixir/threadr/lib/threadr/control_plane/service.ex:1064-1068 | elixir/threadr/lib/threadr/control_plane/tenant_migrations.ex:97-101 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) elixir/threadr/lib/threadr/ingest/discord/consumer.ex:385— elixir/threadr/lib/threadr/ingest/discord/consumer.ex:385-389 | elixir/threadr/lib/threadr/ingest/discord/consumer.ex:619-623 — 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 (5 lines × 2) elixir/threadr/lib/threadr/ingest/discord/consumer.ex:520— elixir/threadr/lib/threadr/ingest/discord/consumer.ex:520-524 | elixir/threadr/lib/threadr/ingest/discord/consumer.ex:542-546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:642— elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:642-646 | elixir/threadr/lib/threadr/tenant_data/history.ex:282-286 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:617— elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:617-621 | elixir/threadr/lib/threadr_web/live/tenant_qa_live/index.ex:788-792 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) elixir/threadr/lib/mix/tasks/threadr.generation.answer.ex:24— elixir/threadr/lib/mix/tasks/threadr.generation.answer.ex:24-32 | elixir/threadr/lib/mix/tasks/threadr.generation.complete.ex:22-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) elixir/threadr/lib/threadr/ml/conversation_qa.ex:48— elixir/threadr/lib/threadr/ml/conversation_qa.ex:48-56 | elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:54-62 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/conversation_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:315— elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:315-323 | elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:340-348 — 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) elixir/threadr/lib/threadr_web/controllers/api/v1/dossier_controller.ex:87— elixir/threadr/lib/threadr_web/controllers/api/v1/dossier_controller.ex:87-95 | elixir/threadr/lib/threadr_web/controllers/api/v1/history_controller.ex:64-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:59— elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:59-67 | elixir/threadr/lib/threadr_web/live/tenant_qa_live/index.ex:49-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex:87— elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex:87-95 | elixir/threadr/lib/threadr_web/controllers/tenant_controller.ex:72-80 — before extracting anything, compare `elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex` and `elixir/threadr/lib/threadr_web/controllers/tenant_controller.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) pkg/api/middleware/admin_auth.go:35— pkg/api/middleware/admin_auth.go:35-43 | pkg/api/middleware/instance.go:21-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) cmd/natsctl/cmd/addAccount.go:13— cmd/natsctl/cmd/addAccount.go:13-21 | cmd/natsctl/cmd/listUsers.go:13-21 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/natsctl/cmd/addAccount.go:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) elixir/threadr/lib/mix/tasks/threadr.smoke.discord_message.ex:270— elixir/threadr/lib/mix/tasks/threadr.smoke.discord_message.ex:270-281 | elixir/threadr/lib/threadr/messaging/smoke.ex:83-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) elixir/threadr/lib/threadr/control_plane/service.ex:1177— elixir/threadr/lib/threadr/control_plane/service.ex:1177-1188 | elixir/threadr/lib/threadr/control_plane/service.ex:1213-1224 — 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) elixir/threadr/lib/threadr/control_plane/service.ex:1193— elixir/threadr/lib/threadr/control_plane/service.ex:1193-1204 | elixir/threadr/lib/threadr/control_plane/service.ex:1226-1237 — 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) elixir/threadr/lib/threadr/control_plane/smoke_server.ex:142— elixir/threadr/lib/threadr/control_plane/smoke_server.ex:142-153 | elixir/threadr/lib/threadr_web/controllers/bot_controller_contract_controller.ex:40-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:504— elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:504-515 | elixir/threadr/lib/threadr/tenant_data/history.ex:227-238 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) elixir/threadr/lib/threadr_web/controllers/api/v1/dossier_controller.ex:16— elixir/threadr/lib/threadr_web/controllers/api/v1/dossier_controller.ex:16-27 | elixir/threadr/lib/threadr_web/controllers/api/v1/dossier_controller.ex:56-67 — 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) elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:40— elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:40-51 | elixir/threadr/lib/threadr_web/live/tenant_history_live/index.ex:42-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
TooManyFunctions: HybridRetriever elixir/threadr/lib/threadr/ml/hybrid_retriever.ex:1— TooManyFunctions — 47 functions. The bar is 30 functions; this is 17 over it, 1.57× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: ConversationSummaryQA elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:1— TooManyFunctions — 39 functions. The bar is 30 functions; this is 9 over it, 1.30× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: ReconstructionCandidates elixir/threadr/lib/threadr/tenant_data/reconstruction_candidates.ex:1— TooManyFunctions — 35 functions. The bar is 30 functions; this is 5 over it, 1.17× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Analysis elixir/threadr/lib/threadr/control_plane/analysis.ex:1— TooManyFunctions — 33 functions. The bar is 30 functions; this is 3 over it, 1.10× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: ConversationAttachment elixir/threadr/lib/threadr/tenant_data/conversation_attachment.ex:1— TooManyFunctions — 32 functions. The bar is 30 functions; this is 2 over it, 1.07× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: History elixir/threadr/lib/threadr/tenant_data/history.ex:1— TooManyFunctions — 31 functions. The bar is 30 functions; this is 1 over it, 1.03× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
Duplicated block (11 lines × 2) elixir/threadr/lib/threadr/ingest/bot_qa.ex:592— elixir/threadr/lib/threadr/ingest/bot_qa.ex:592-602 | elixir/threadr/lib/threadr/ingest/bot_qa.ex:633-643 — 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) elixir/threadr/lib/threadr/ml/actor_qa.ex:221— elixir/threadr/lib/threadr/ml/actor_qa.ex:221-231 | elixir/threadr/lib/threadr/ml/actor_qa.ex:257-267 — 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) elixir/threadr/lib/threadr/ml/generation/chat_completions_provider.ex:59— elixir/threadr/lib/threadr/ml/generation/chat_completions_provider.ex:59-69 | elixir/threadr/lib/threadr/ml/generation/gemini_provider.ex:96-106 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:283— elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:283-293 | elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:297-307 — 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) elixir/threadr/lib/threadr/tenant_data/ingest.ex:365— elixir/threadr/lib/threadr/tenant_data/ingest.ex:365-375 | elixir/threadr/lib/threadr/tenant_data/ingest.ex:414-424 — 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) elixir/threadr/lib/threadr/tenant_data/ingest.ex:448— elixir/threadr/lib/threadr/tenant_data/ingest.ex:448-458 | elixir/threadr/lib/threadr/tenant_data/ingest.ex:469-479 — 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) elixir/threadr/lib/threadr/ml/constrained_qa.ex:469— elixir/threadr/lib/threadr/ml/constrained_qa.ex:469-476 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:546-553 — 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) elixir/threadr/lib/threadr/tenant_data/extraction.ex:99— elixir/threadr/lib/threadr/tenant_data/extraction.ex:99-106 | elixir/threadr/lib/threadr/tenant_data/extraction.ex:153-160 — 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) elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex:103— elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex:103-110 | elixir/threadr/lib/threadr/ml/qa_intent.ex:154-161 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex` and `elixir/threadr/lib/threadr/ml/qa_intent.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) elixir/threadr/lib/threadr/ml/embeddings.ex:35— elixir/threadr/lib/threadr/ml/embeddings.ex:35-42 | elixir/threadr/lib/threadr/tenant_data/extraction.ex:72-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:281— elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:281-288 | elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex:352-359 — `elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex` and `elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 54 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) elixir/threadr/lib/threadr/ml/actor_qa.ex:35— elixir/threadr/lib/threadr/ml/actor_qa.ex:35-40 | elixir/threadr/lib/threadr/ml/actor_qa.ex:48-53 — 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) elixir/threadr/lib/threadr/ml/constrained_qa.ex:511— elixir/threadr/lib/threadr/ml/constrained_qa.ex:511-517 | elixir/threadr/lib/threadr/ml/conversation_qa.ex:203-208 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/constrained_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_qa.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:589— elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:589-594 | elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:626-631 — 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) elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex:77— elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex:77-82 | elixir/threadr/lib/threadr/ml/qa_intent.ex:86-91 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex` and `elixir/threadr/lib/threadr/ml/qa_intent.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:36— elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:36-41 | elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex:41-46 — `elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex` and `elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 54 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
TodoComment k8s/operators/ircbot-operator/internal/controller/ircbot_controller_test.go:41— // TODO(user):Modify as needed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment k8s/operators/ircbot-operator/internal/controller/ircbot_controller_test.go:69— // TODO(user): Cleanup logic after each test, like removing the resource instance. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment k8s/operators/ircbot-operator/internal/controller/ircbot_controller_test.go:92— // TODO(user): Add more specific assertions depending on your controller's reconciliation logic. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment pkg/adapters/messages/batch_processor.go:105— // TODO: send message_processing to Mistral in chunks and handle the response — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (17 lines × 2) elixir/threadr/lib/threadr/compare_delta.ex:14— elixir/threadr/lib/threadr/compare_delta.ex:14-30 | elixir/threadr/lib/threadr/compare_delta.ex:43-59 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) elixir/threadr/lib/threadr/ingest.ex:68— elixir/threadr/lib/threadr/ingest.ex:68-84 | elixir/threadr/lib/threadr/ingest.ex:98-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) elixir/threadr/lib/threadr/ml/conversation_qa.ex:83— elixir/threadr/lib/threadr/ml/conversation_qa.ex:83-99 | elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:120-136 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/conversation_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:69— elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:69-85 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:101-117 — 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) elixir/threadr/lib/threadr/history_request.ex:64— elixir/threadr/lib/threadr/history_request.ex:64-73 | elixir/threadr/lib/threadr/history_request.ex:80-89 — 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) elixir/threadr/lib/threadr/ingest/discord/consumer.ex:601— elixir/threadr/lib/threadr/ingest/discord/consumer.ex:601-610 | elixir/threadr/lib/threadr/ingest/discord/consumer.ex:629-638 — 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) cmd/bots/IRC/main.go:38— cmd/bots/IRC/main.go:38-47 | cmd/bots/discord/main.go:28-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) pkg/api/middleware/admin_auth.go:47— pkg/api/middleware/admin_auth.go:47-56 | pkg/api/middleware/instance.go:33-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/api/middleware/admin_auth.go:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Hotspot: elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:18— elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in updateSelectionDetails at line 18. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-12-10..2026-03-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-10 18:46:07 +00:00' --until='2026-03-10 18:46:07 +00:00' --full-history --no-merges -- elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:10— elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ThreadrGraphRenderer.constructor at line 10. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-12-10..2026-03-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-10 18:46:07 +00:00' --until='2026-03-10 18:46:07 +00:00' --full-history --no-merges -- elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:265— elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in edgeColor at line 265. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-12-10..2026-03-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-10 18:46:07 +00:00' --until='2026-03-10 18:46:07 +00:00' --full-history --no-merges -- elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) elixir/threadr/lib/threadr/control_plane/analysis.ex:469— elixir/threadr/lib/threadr/control_plane/analysis.ex:469-482 | elixir/threadr/lib/threadr/control_plane/analysis.ex:509-522 | elixir/threadr/lib/threadr/control_plane/service.ex:1077-1090 | elixir/threadr/lib/threadr/control_plane/service.ex:1094-1107 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:88— elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:88-115 | elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:119-145 | elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:152-179 | elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:183-209 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) elixir/threadr/lib/threadr_web/controllers/api/v1/me_controller.ex:7— elixir/threadr/lib/threadr_web/controllers/api/v1/me_controller.ex:7-27 | elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex:7-20 | elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex:24-39 | elixir/threadr/lib/threadr_web/controllers/tenant_controller.ex:7-20 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (14 lines × 2) elixir/threadr/lib/threadr/ml/conversation_qa.ex:167— elixir/threadr/lib/threadr/ml/conversation_qa.ex:167-180 | elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:157-170 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/conversation_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex:86— elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex:86-99 | elixir/threadr/lib/threadr/ml/qa_intent.ex:95-108 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex` and `elixir/threadr/lib/threadr/ml/qa_intent.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:134— elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:134-147 | elixir/threadr/lib/threadr_web/controllers/bot_status_controller.ex:43-56 — before extracting anything, compare `elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex` and `elixir/threadr/lib/threadr_web/controllers/bot_status_controller.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review.ex:53— elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review.ex:53-59 | elixir/threadr/lib/threadr/tenant_data/conversation_relationship_recompute.ex:75-81 | elixir/threadr/lib/threadr/tenant_data/conversation_summarizer.ex:57-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (7 lines × 3) elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex:67— elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex:67-73 | elixir/threadr/lib/threadr/ml/interaction_qa_intent.ex:57-63 | elixir/threadr/lib/threadr/ml/qa_intent.ex:76-82 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex` and `elixir/threadr/lib/threadr/ml/qa_intent.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) elixir/threadr/lib/threadr/ml/actor_qa.ex:686— elixir/threadr/lib/threadr/ml/actor_qa.ex:686-692 | elixir/threadr/lib/threadr/ml/conversation_qa.ex:357-363 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:299-305 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_qa.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) elixir/threadr/lib/threadr/ml/constrained_qa.ex:366— elixir/threadr/lib/threadr/ml/constrained_qa.ex:366-372 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:396-402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) elixir/threadr/lib/threadr_web/live/tenant_history_live/index.ex:60— elixir/threadr/lib/threadr_web/live/tenant_history_live/index.ex:60-66 | elixir/threadr/lib/threadr_web/live/tenant_history_live/index.ex:100-106 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) elixir/threadr/lib/threadr/control_plane/analysis.ex:559— elixir/threadr/lib/threadr/control_plane/analysis.ex:559-565 | elixir/threadr/lib/threadr/control_plane/service.ex:1330-1336 — before extracting anything, compare `elixir/threadr/lib/threadr/control_plane/analysis.ex` and `elixir/threadr/lib/threadr/control_plane/service.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) elixir/threadr/lib/mix/tasks/threadr.embeddings.generate.ex:38— elixir/threadr/lib/mix/tasks/threadr.embeddings.generate.ex:38-44 | elixir/threadr/lib/mix/tasks/threadr.generation.answer.ex:52-58 | elixir/threadr/lib/mix/tasks/threadr.generation.answer_tenant.ex:38-44 | elixir/threadr/lib/mix/tasks/threadr.generation.complete.ex:34-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (7 lines × 4) elixir/threadr/lib/threadr/control_plane/bot_status_observer.ex:56— elixir/threadr/lib/threadr/control_plane/bot_status_observer.ex:56-62 | elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review_dispatcher.ex:63-69 | elixir/threadr/lib/threadr/tenant_data/conversation_relationship_dispatcher.ex:63-69 | elixir/threadr/lib/threadr/tenant_data/conversation_summary_dispatcher.ex:64-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (7 lines × 4) elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex:57— elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex:57-63 | elixir/threadr/lib/threadr/ml/conversation_summary_qa_intent.ex:99-105 | elixir/threadr/lib/threadr/ml/interaction_qa_intent.ex:47-53 | elixir/threadr/lib/threadr/ml/qa_intent.ex:23-29 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/conversation_qa_intent.ex` and `elixir/threadr/lib/threadr/ml/qa_intent.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
X2 · Cancellation propagation· Function without context.Context · ×3
Function without context.Context: AccessSecureEndpoint cmd/client/admin/secure.go:11— `AccessSecureEndpoint` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: GetClaims cmd/client/admin/claims.go:12— `GetClaims` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: SendClaimsUpdate cmd/client/admin/claims.go:51— `SendClaimsUpdate` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Repeated repair: elixir/threadr/lib/threadr/ingest/bot_qa.ex elixir/threadr/lib/threadr/ingest/bot_qa.ex:250— elixir/threadr/lib/threadr/ingest/bot_qa.ex changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is BotQA.answer_qa_request at line 250), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “wip: fixed the single-actor question path”; “wip: question answering bugs”; “fix: split long irc bot replies”; “fix: restore discord bot replies”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-12-10..2026-03-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-10 18:46:07 +00:00' --until='2026-03-10 18:46:07 +00:00' --full-history --no-merges -- elixir/threadr/lib/threadr/ingest/bot_qa.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: elixir/threadr/lib/threadr/ml/conversation_qa.ex elixir/threadr/lib/threadr/ml/conversation_qa.ex:25— elixir/threadr/lib/threadr/ml/conversation_qa.ex changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is ConversationQA.answer_question at line 25), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: convo bug”; “fix: tolerate missing reconstruction tables”; “wip: qa bug fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-12-10..2026-03-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-10 18:46:07 +00:00' --until='2026-03-10 18:46:07 +00:00' --full-history --no-merges -- elixir/threadr/lib/threadr/ml/conversation_qa.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
REDACTED
REDACTED
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) elixir/threadr/lib/threadr/ml/actor_qa.ex:470— elixir/threadr/lib/threadr/ml/actor_qa.ex:470-493 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:806-823 | elixir/threadr/lib/threadr/ml/conversation_qa.ex:116-155 | elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:82-110 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:196-218 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:496— elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:496-515 | elixir/threadr/lib/threadr/tenant_data/history.ex:220-239 | elixir/threadr/lib/threadr/tenant_data/history.ex:245-267 | elixir/threadr/lib/threadr/tenant_data/reconstruction_candidates.ex:222-247 | elixir/threadr/lib/threadr/tenant_data/reconstruction_candidates.ex:253-280 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (19 lines × 3) elixir/threadr/lib/threadr/ml/actor_qa.ex:199— elixir/threadr/lib/threadr/ml/actor_qa.ex:199-217 | elixir/threadr/lib/threadr/ml/actor_qa.ex:234-252 | elixir/threadr/lib/threadr/ml/actor_qa.ex:270-288 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (19 lines × 3) elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review_dispatcher.ex:73— elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review_dispatcher.ex:73-91 | elixir/threadr/lib/threadr/tenant_data/conversation_relationship_dispatcher.ex:73-91 | elixir/threadr/lib/threadr/tenant_data/conversation_summary_dispatcher.ex:74-92 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (18 lines × 2) elixir/threadr/lib/threadr/ml/actor_qa.ex:520— elixir/threadr/lib/threadr/ml/actor_qa.ex:520-537 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:245-262 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/semantic_qa.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) elixir/threadr/lib/threadr/tenant_data/history.ex:220— elixir/threadr/lib/threadr/tenant_data/history.ex:220-237 | elixir/threadr/lib/threadr/tenant_data/reconstruction_candidates.ex:222-239 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) elixir/threadr/lib/threadr/ml/actor_qa.ex:499— elixir/threadr/lib/threadr/ml/actor_qa.ex:499-514 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:224-239 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/semantic_qa.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) elixir/threadr/lib/threadr/tenant_data/ingest.ex:377— elixir/threadr/lib/threadr/tenant_data/ingest.ex:377-392 | elixir/threadr/lib/threadr/tenant_data/ingest.ex:426-441 — 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) elixir/threadr/lib/threadr/control_plane/analysis.ex:528— elixir/threadr/lib/threadr/control_plane/analysis.ex:528-542 | elixir/threadr/lib/threadr/control_plane/service.ex:1273-1287 — before extracting anything, compare `elixir/threadr/lib/threadr/control_plane/analysis.ex` and `elixir/threadr/lib/threadr/control_plane/service.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) elixir/threadr/lib/threadr/ml/constrained_qa.ex:809— elixir/threadr/lib/threadr/ml/constrained_qa.ex:809-823 | elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:94-108 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/constrained_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) elixir/threadr/lib/threadr/control_plane/smoke_server.ex:157— elixir/threadr/lib/threadr/control_plane/smoke_server.ex:157-169 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:130-142 | elixir/threadr/lib/threadr_web/controllers/bot_status_controller.ex:39-51 — before extracting anything, compare `elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex` and `elixir/threadr/lib/threadr_web/controllers/bot_status_controller.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) elixir/threadr/lib/threadr/ml/actor_qa.ex:523— elixir/threadr/lib/threadr/ml/actor_qa.ex:523-535 | elixir/threadr/lib/threadr/ml/conversation_qa.ex:310-322 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:248-260 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_qa.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) elixir/threadr/lib/threadr/ml/actor_qa.ex:478— elixir/threadr/lib/threadr/ml/actor_qa.ex:478-488 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:808-818 | elixir/threadr/lib/threadr/ml/conversation_qa.ex:139-149 | elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:93-103 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:203-213 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_qa.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) elixir/threadr/lib/threadr/ml/constrained_qa.ex:375— elixir/threadr/lib/threadr/ml/constrained_qa.ex:375-385 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:405-415 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:523-533 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:554-564 | elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:283-293 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/constrained_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (3–5 lines × 3) elixir/threadr/lib/threadr/ml/actor_qa.ex:574— elixir/threadr/lib/threadr/ml/actor_qa.ex:574-578 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:366-370 | elixir/threadr/lib/threadr/tenant_data/history.ex:309-311 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/semantic_qa.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (3–5 lines × 3) elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:81— elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:81-85 | elixir/threadr/lib/threadr_web/live/tenant_graph_live/index.ex:142-146 | elixir/threadr/lib/threadr_web/live/tenant_qa_live/index.ex:66-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (5 lines × 3) elixir/threadr/lib/threadr/ingest.ex:132— elixir/threadr/lib/threadr/ingest.ex:132-136 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:871-875 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:881-885 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 3) elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:608— elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:608-612 | elixir/threadr/lib/threadr_web/live/tenant_history_live/index.ex:759-763 | elixir/threadr/lib/threadr_web/live/tenant_qa_live/index.ex:779-783 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Outbound HTTP without resilience elixir/threadr/lib/mix/tasks/threadr.smoke.discord_message.ex:339— `Req.post!(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience pkg/adapters/messages/mistral7b_analyzer.go:49— `http.Post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Duplicated block (6 lines × 2 locations) elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:115— elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:115 · elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:124 — 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 locations) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:668— elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:668 · elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:694 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark elixir/threadr/lib/threadr_web/components/layouts/root.html.heex:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
C1 · Data Protection· No data-protection/encryption · ×1
No data-protection/encryption elixir/threadr/lib/threadr/control_plane/user.ex:119— No encryption usage (Cloak.Ecto encrypted field types, a Cloak vault, Plug.Crypto's message encryptor, :crypto ciphers that encrypt, libsodium boxes) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
updateSelectionDetails (cyclomatic 26) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:18— updateSelectionDetails has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
tooltipText (cyclomatic 25) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:515— tooltipText has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
nodeLabel (cyclomatic 22) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:629— nodeLabel has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
renderTopRelationshipsSection (cyclomatic 19) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:620— renderTopRelationshipsSection has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 625). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
decodeArrowGraph (cyclomatic 19) elixir/threadr/assets/js/lib/threadr_graph/lifecycle_stream_methods.js:41— decodeArrowGraph has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
renderGraph (cyclomatic 18) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:12— renderGraph has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 28 function items inside it that branch (onViewStateChange, getSourcePosition, getTargetPosition, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
main.main (cyclomatic 17) k8s/operators/ircbot-operator/cmd/threadrbot-smoke/main.go:38— main.main has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. 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.
ThreadrGraphRenderer.constructor (cyclomatic 17) elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:10— ThreadrGraphRenderer.constructor has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Index.bot_form (cyclomatic 16) elixir/threadr/lib/threadr_web/live/tenant_bot_live/index.ex:598— Index.bot_form has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
renderNodeDossier (cyclomatic 16) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:412— renderNodeDossier has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
clusterToNode (cyclomatic 16) elixir/threadr/assets/js/lib/threadr_graph/layout_cluster_methods.js:113— clusterToNode has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Retired release: jetstream — `:jetstream` is pinned to 0.0.9 in the committed REDACTED, and the publisher retired it — the package was renamed on hex.pm — "Merged into the main nats.ex (gnat) library. Use Gnat.Jetstream from the :gnat package instead.". A retired release is one the publisher has asked you to stop using. Move off it and commit the updated lockfile.
Unbounded dependency requirement: postgrex — Runtime dependency `:postgrex` is declared `">= 0.0.0"` in elixir/threadr/mix.exs, which has no upper bound — every future MAJOR release of `:postgrex` satisfies it, so the next unlocked resolve can pull a breaking change. Use `~>` (e.g. `"~> 1.0"`) to bound the requirement to a compatible range.
decodeArrowGraph (cognitive 24) elixir/threadr/assets/js/lib/threadr_graph/lifecycle_stream_methods.js:41— decodeArrowGraph has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, if/else 3 (6 pts), error handling 1 (4 pts), loops 1 (nesting depth added 6). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
edgeColor (cognitive 23) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:265— edgeColor has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 7 (9 pts), 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.
IRCAdapter.Send (cognitive 22) REDACTED:109— IRCAdapter.Send has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 1 (2 pts), 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.
ThreadrBotReconciler.Reconcile (cognitive 22) k8s/operators/ircbot-operator/internal/controller/threadrbot_controller.go:45— ThreadrBotReconciler.Reconcile has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 1, 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.
updateSelectionDetails (cognitive 21) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:18— updateSelectionDetails has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 14, ternaries 4, if/else 2, other 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
tooltipText (cognitive 20) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:515— tooltipText has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, if/else 6, ternaries 3 (6 pts) (nesting depth added 3). 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.
ConversationRelationshipRecompute.recompute_conversation_relationships (cognitive 18) elixir/threadr/lib/threadr/tenant_data/conversation_relationship_recompute.ex:25— ConversationRelationshipRecompute.recompute_conversation_relationships has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 3 (5 pts) (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.
threadr_graph_exec::compute_three_hop_mask (cognitive 18) elixir/threadr/assets/wasm/threadr_graph_exec/src/lib.rs:62— threadr_graph_exec::compute_three_hop_mask has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (6 pts), boolean chains 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.
renderTopRelationshipsSection (cognitive 18) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:620— renderTopRelationshipsSection has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 6, if/else 3. Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 625). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
main.main (cognitive 17) k8s/operators/ircbot-operator/cmd/threadrbot-smoke/main.go:38— main.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 2 (nesting depth added 1). Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. 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.
renderGraph (cognitive 17) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:12— renderGraph has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 4, ternaries 2. Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 28 function items inside it that branch (onViewStateChange, getSourcePosition, getTargetPosition, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
nodeLabel (cognitive 17) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:629— nodeLabel has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 6, ternaries 3 (6 pts), if/else 5 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.main (cognitive 16) k8s/operators/ircbot-operator/cmd/main.go:56— main.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (16 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
main.waitForContractRealization (cognitive 16) k8s/operators/ircbot-operator/cmd/threadrbot-smoke/main.go:145— main.waitForContractRealization has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (3 pts), 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.
ThreadrGraphRenderer.constructor (cognitive 16) elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:10— ThreadrGraphRenderer.constructor has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 16. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
FunctionTooLong: threadr_graph_nif::encode_snapshot elixir/threadr/native/threadr_graph_nif/src/lib.rs:59— FunctionTooLong — threadr_graph_nif::encode_snapshot runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Near-duplicate member pair (24 shared lines) elixir/threadr/lib/threadr/ml/actor_qa.ex:555— elixir/threadr/lib/threadr/ml/actor_qa.ex:555-584 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:347-376 — These two members are variants of one another: 24 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:7— elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:7-30 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:34-59 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:63-91 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:95-123 | elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex:43-66 | elixir/threadr/lib/threadr_web/controllers/bot_controller_contract_controller.ex:18-36 | elixir/threadr/lib/threadr_web/controllers/bot_status_controller.ex:7-35 | elixir/threadr/lib/threadr_web/controllers/tenant_controller.ex:24-47 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) elixir/threadr/lib/threadr/ml/constrained_qa.ex:362— elixir/threadr/lib/threadr/ml/constrained_qa.ex:362-388 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:392-418 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:422-495 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:499-537 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:541-582 | elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:274-297 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (22 lines × 2) elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:249— elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:249-270 | elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex:320-341 — `elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex` and `elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 54 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (21 lines × 2) elixir/threadr/lib/threadr/tenant_data/conversation_attachment.ex:281— elixir/threadr/lib/threadr/tenant_data/conversation_attachment.ex:281-301 | elixir/threadr/lib/threadr/tenant_data/pending_item_tracking.ex:187-207 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (20 lines × 3) elixir/threadr/lib/threadr/tenant_data/graph_layout.ex:118— elixir/threadr/lib/threadr/tenant_data/graph_layout.ex:118-137 | elixir/threadr/lib/threadr/tenant_data/graph_layout.ex:141-160 | elixir/threadr/lib/threadr/tenant_data/graph_layout.ex:164-183 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (20 lines × 2) elixir/threadr/lib/threadr/tenant_data/history.ex:245— elixir/threadr/lib/threadr/tenant_data/history.ex:245-264 | elixir/threadr/lib/threadr/tenant_data/reconstruction_candidates.ex:253-272 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19 lines × 5) elixir/threadr/lib/threadr_web/controllers/api/v1/qa_controller.ex:14— elixir/threadr/lib/threadr_web/controllers/api/v1/qa_controller.ex:14-32 | elixir/threadr/lib/threadr_web/controllers/api/v1/qa_controller.ex:41-59 | elixir/threadr/lib/threadr_web/controllers/api/v1/qa_controller.ex:75-93 | elixir/threadr/lib/threadr_web/controllers/api/v1/qa_controller.ex:103-121 | elixir/threadr/lib/threadr_web/controllers/api/v1/qa_controller.ex:130-148 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–19 lines × 3) elixir/threadr/lib/threadr/ml/actor_reference.ex:118— elixir/threadr/lib/threadr/ml/actor_reference.ex:118-136 | elixir/threadr/lib/threadr/ml/actor_reference.ex:140-158 | elixir/threadr/lib/threadr/ml/actor_reference.ex:163-176 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17–18 lines × 3) elixir/threadr/lib/threadr/tenant_data/graph.ex:240— elixir/threadr/lib/threadr/tenant_data/graph.ex:240-256 | elixir/threadr/lib/threadr/tenant_data/graph.ex:282-299 | elixir/threadr/lib/threadr/tenant_data/graph.ex:324-341 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15–16 lines × 3) elixir/threadr/lib/threadr/ml/actor_qa.ex:470— elixir/threadr/lib/threadr/ml/actor_qa.ex:470-485 | elixir/threadr/lib/threadr/ml/conversation_qa.ex:131-146 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:196-210 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_qa.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 6) elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:17— elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:17-30 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:46-59 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:78-91 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:110-123 | elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex:53-66 | elixir/threadr/lib/threadr_web/controllers/tenant_controller.ex:34-47 — before extracting anything, compare `elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex` and `elixir/threadr/lib/threadr_web/controllers/tenant_controller.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) elixir/threadr/lib/threadr/ml/actor_qa.ex:559— elixir/threadr/lib/threadr/ml/actor_qa.ex:559-572 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:351-364 | elixir/threadr/lib/threadr/tenant_data/history.ex:294-307 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/semantic_qa.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–14 lines × 2) elixir/threadr/lib/threadr_web/controllers/api/v1/history_controller.ex:34— elixir/threadr/lib/threadr_web/controllers/api/v1/history_controller.ex:34-43 | elixir/threadr/lib/threadr_web/controllers/api/v1/qa_controller.ex:70-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 5) elixir/threadr/lib/threadr/ml/constrained_qa.ex:376— elixir/threadr/lib/threadr/ml/constrained_qa.ex:376-388 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:406-418 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:450-462 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:478-490 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:555-567 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 4) elixir/threadr/lib/threadr/control_plane/analysis.ex:470— elixir/threadr/lib/threadr/control_plane/analysis.ex:470-482 | elixir/threadr/lib/threadr/control_plane/analysis.ex:510-522 | elixir/threadr/lib/threadr/control_plane/service.ex:1078-1090 | elixir/threadr/lib/threadr/control_plane/service.ex:1095-1107 — before extracting anything, compare `elixir/threadr/lib/threadr/control_plane/analysis.ex` and `elixir/threadr/lib/threadr/control_plane/service.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–13 lines × 3) elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review.ex:35— elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review.ex:35-47 | elixir/threadr/lib/threadr/tenant_data/conversation_relationship_recompute.ex:56-68 | elixir/threadr/lib/threadr/tenant_data/conversation_summarizer.ex:44-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (11–13 lines × 2) elixir/threadr/lib/threadr/tenant_data/ingest.ex:534— elixir/threadr/lib/threadr/tenant_data/ingest.ex:534-544 | elixir/threadr/lib/threadr/tenant_data/ingest.ex:576-588 — 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) elixir/threadr/lib/threadr/tenant_data/reconstruction_candidates.ex:235— elixir/threadr/lib/threadr/tenant_data/reconstruction_candidates.ex:235-247 | elixir/threadr/lib/threadr/tenant_data/reconstruction_candidates.ex:268-280 — 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–13 lines × 2) elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:54— elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:54-65 | elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex:63-75 — `elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex` and `elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 54 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12 lines × 4) elixir/threadr/lib/threadr/ml/constrained_qa.ex:374— elixir/threadr/lib/threadr/ml/constrained_qa.ex:374-385 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:404-415 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:522-533 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:553-564 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11–12 lines × 4) elixir/threadr/lib/threadr_web/controllers/api/v1/me_controller.ex:16— elixir/threadr/lib/threadr_web/controllers/api/v1/me_controller.ex:16-27 | elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex:10-20 | elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex:29-39 | elixir/threadr/lib/threadr_web/controllers/tenant_controller.ex:10-20 — before extracting anything, compare `elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex` and `elixir/threadr/lib/threadr_web/controllers/tenant_controller.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) elixir/threadr/lib/threadr/ml/generation/anthropic_provider.ex:20— elixir/threadr/lib/threadr/ml/generation/anthropic_provider.ex:20-31 | elixir/threadr/lib/threadr/ml/generation/chat_completions_provider.ex:27-38 | elixir/threadr/lib/threadr/ml/generation/gemini_provider.ex:19-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (11 lines × 4) elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:90— elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:90-100 | elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:121-131 | elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:154-164 | elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:185-195 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) elixir/threadr/lib/threadr/ml/actor_qa.ex:502— elixir/threadr/lib/threadr/ml/actor_qa.ex:502-512 | elixir/threadr/lib/threadr/ml/conversation_qa.ex:291-301 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:227-237 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_qa.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7–11 lines × 2) elixir/threadr/lib/threadr/tenant_data/ingest.ex:133— elixir/threadr/lib/threadr/tenant_data/ingest.ex:133-143 | elixir/threadr/lib/threadr/tenant_data/ingest.ex:172-178 — 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–11 lines × 2) elixir/threadr/lib/threadr/tenant_data/ingest.ex:247— elixir/threadr/lib/threadr/tenant_data/ingest.ex:247-257 | elixir/threadr/lib/threadr/tenant_data/ingest.ex:334-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 (10 lines × 6) elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:10— elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:10-19 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:39-48 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:66-75 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:98-107 | elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex:46-55 | elixir/threadr/lib/threadr_web/controllers/tenant_controller.ex:27-36 — before extracting anything, compare `elixir/threadr/lib/threadr_web/controllers/api/v1/tenant_controller.ex` and `elixir/threadr/lib/threadr_web/controllers/tenant_controller.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:72— elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:72-80 | elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex:104-112 | elixir/threadr/lib/threadr_web/controllers/bot_controller_contract_controller.ex:22-30 | elixir/threadr/lib/threadr_web/controllers/bot_status_controller.ex:11-19 — before extracting anything, compare `elixir/threadr/lib/threadr_web/controllers/api/v1/bot_controller.ex` and `elixir/threadr/lib/threadr_web/controllers/bot_status_controller.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6–8 lines × 3) elixir/threadr/lib/threadr/ml/constrained_qa.ex:504— elixir/threadr/lib/threadr/ml/constrained_qa.ex:504-511 | elixir/threadr/lib/threadr/ml/conversation_qa.ex:75-80 | elixir/threadr/lib/threadr/ml/interaction_qa.ex:122-127 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/constrained_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_qa.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) elixir/threadr/lib/threadr/ml/conversation_qa.ex:48— elixir/threadr/lib/threadr/ml/conversation_qa.ex:48-55 | elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:54-61 | elixir/threadr/lib/threadr/ml/interaction_qa.ex:50-57 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/conversation_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 5) elixir/threadr/lib/threadr/events/chat_context_event.ex:27— elixir/threadr/lib/threadr/events/chat_context_event.ex:27-36 | elixir/threadr/lib/threadr/events/chat_message.ex:37-46 | elixir/threadr/lib/threadr/events/envelope.ex:50-59 | elixir/threadr/lib/threadr/events/ingest_command.ex:25-34 | elixir/threadr/lib/threadr/events/processing_result.ex:26-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
Duplicated block (8 lines × 8) elixir/threadr/lib/threadr/ml/actor_qa.ex:673— elixir/threadr/lib/threadr/ml/actor_qa.ex:673-680 | elixir/threadr/lib/threadr/ml/actor_reference.ex:254-261 | elixir/threadr/lib/threadr/ml/constrained_qa.ex:1115-1122 | elixir/threadr/lib/threadr/ml/conversation_qa.ex:369-376 | elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:426-433 | elixir/threadr/lib/threadr/ml/hybrid_retriever.ex:519-526 | elixir/threadr/lib/threadr/ml/interaction_qa.ex:347-354 | elixir/threadr/lib/threadr/ml/semantic_qa.ex:286-293 — before extracting anything, compare `elixir/threadr/lib/threadr/ml/actor_qa.ex` and `elixir/threadr/lib/threadr/ml/conversation_qa.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18–19 lines × 3) cmd/client/admin/claims.go:24— cmd/client/admin/claims.go:24-42 | cmd/client/admin/claims.go:68-86 | cmd/client/admin/secure.go:20-37 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/client/admin/claims.go:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cmd/client/admin/claims.go:21` calls `Printf` and `cmd/client/admin/secure.go:17` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
Duplicated block (23 lines × 2 locations) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:815— elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:815 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:856 — 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 (22 lines × 2 locations) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:490— elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:490 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:711 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:35— elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:35 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:165 — 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 locations) elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:225— elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:225 · elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:182 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (13 lines × 3 locations) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:756— elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:756 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:787 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:830 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 3 locations) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:738— elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:738 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:770 · elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:844 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 2 locations) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:193— elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:193 · elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:310 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (7 lines × 2 locations) elixir/threadr/assets/js/lib/threadr_graph/layout_cluster_methods.js:51— elixir/threadr/assets/js/lib/threadr_graph/layout_cluster_methods.js:51 · elixir/threadr/assets/js/lib/threadr_graph/layout_cluster_methods.js:81 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (5 lines × 2 locations) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:520— elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:520 · elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:532 — 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.
Complex function updateSelectionDetails (cyclomatic 26, cognitive 21) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:18— updateSelectionDetails has cyclomatic complexity 26 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function tooltipText (cyclomatic 25, cognitive 20) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:515— tooltipText has cyclomatic complexity 25 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function nodeLabel (cyclomatic 22, cognitive 17) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:629— nodeLabel has cyclomatic complexity 22 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function decodeArrowGraph (cyclomatic 19, cognitive 24) elixir/threadr/assets/js/lib/threadr_graph/lifecycle_stream_methods.js:41— decodeArrowGraph has cyclomatic complexity 19 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function constructor (cyclomatic 17, cognitive 16) elixir/threadr/assets/js/lib/threadr_graph/ThreadrGraphRenderer.js:10— constructor has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 16, cognitive 15) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:625— (anonymous) has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderNodeDossier (cyclomatic 16, cognitive 12) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:412— renderNodeDossier has cyclomatic complexity 16 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function edgeColor (cyclomatic 15, cognitive 23) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:265— edgeColor has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function relationshipEdgePreserve (cyclomatic 15, cognitive 12) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:442— relationshipEdgePreserve has cyclomatic complexity 15 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function historyHref (cyclomatic 15, cognitive 11) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:539— historyHref has cyclomatic complexity 15 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function clusterToNode (cyclomatic 14, cognitive 13) elixir/threadr/assets/js/lib/threadr_graph/layout_cluster_methods.js:113— clusterToNode has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function shouldShowNeighborhoodLabel (cyclomatic 14, cognitive 13) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:605— shouldShowNeighborhoodLabel has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function shouldShowNodeLabel (cyclomatic 13, cognitive 11) elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:576— shouldShowNodeLabel has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function showMessagesForFocus (cyclomatic 11, cognitive 11) elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:160— showMessagesForFocus has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js · ×1
elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js: 736 lines of code elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:1— elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js has 736 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js · ×1
elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js: 632 lines of code elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:1— elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js has 632 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint or typecheck script — test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
X2 · Cancellation propagation· Async function without AbortSignal · ×1
Async function without AbortSignal: init elixir/threadr/assets/js/wasm/threadr_graph_exec_runtime.js:10— `init` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×1
Untrusted text written into markup unescaped elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js:590— `this.escapeAttribute(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Orphaned file elixir/threadr/lib/threadr_web/live/tenant_history_live/index.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/tenant_data/ingest.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr_web/live/tenant_bot_live/index.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/ingest/discord/consumer.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/ml/actor_qa.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/tenant_data/graph_inspector.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/tenant_data/graph_snapshot.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/tenant_data/graph.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/config/runtime.exs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/ml/hybrid_retriever.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/control_plane/analysis.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/ingest/bot_qa.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/tenant_data/conversation_attachment.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/tenant_data/reconstruction_candidates.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file k8s/operators/ircbot-operator/internal/controller/threadrbot_controller.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/tenant_data/conversation_relationship_recompute.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr_web/components/core_components.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/ingest/irc/agent.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/ml/conversation_qa.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr/tenant_data/history.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/mix/tasks/threadr.seed.demo.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file elixir/threadr/lib/threadr_web/live/tenant_graph_live/index.ex:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:3— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:3— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:3— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:302— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:567— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:615— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:16— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:8— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:4— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile k8s/operators/ircbot-operator/config/default/manager_config_patch.yaml:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:15— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:8— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:8— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile k8s/threadr/bot-operator/remove_auth_proxy_patch.yaml:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
Duplicated predicate elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:236— `(settings.max_tokens && to_string(settings.max_tokens)) || ""` appears character-identically in 2 files — elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex, elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex:235— `(settings.temperature && to_string(settings.temperature)) || ""` appears character-identically in 2 files — elixir/threadr/lib/threadr_web/live/system_llm_settings_live/index.ex, elixir/threadr/lib/threadr_web/live/tenant_llm_settings_live/index.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/events/chat_context_event.ex:40— `Map.get(attrs, key) || Map.get(attrs, Atom.to_string(key)) || default` appears character-identically in 8 files — elixir/threadr/lib/threadr/events/chat_context_event.ex, elixir/threadr/lib/threadr/events/chat_message.ex, elixir/threadr/lib/threadr/events/envelope.ex, elixir/threadr/lib/threadr/events/ingest_command.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:41— `System.get_env("THREADR_DB_HOST") || "localhost"` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:40— `System.get_env("THREADR_DB_PASSWORD") || "postgres"` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:42— `System.get_env("THREADR_DB_PORT") || "55432"` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:39— `System.get_env("THREADR_DB_USER") || "postgres"` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/ml/conversation_qa.ex:77— `cm1.conversation_id == c.id and cm1.member_kind == "actor"` appears character-identically in 2 files — elixir/threadr/lib/threadr/ml/conversation_qa.ex, elixir/threadr/lib/threadr/tenant_data/conversation_relationship_recompute.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/ml/conversation_qa.ex:79— `cm2.conversation_id == c.id and cm2.member_kind == "actor"` appears character-identically in 2 files — elixir/threadr/lib/threadr/ml/conversation_qa.ex, elixir/threadr/lib/threadr/tenant_data/conversation_relationship_recompute.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/control_plane/analysis.ex:535— `config.endpoint || Threadr.ML.Generation.ProviderResolver.default_endpoint(config.provider_name)` appears character-identically in 2 files — elixir/threadr/lib/threadr/control_plane/analysis.ex, elixir/threadr/lib/threadr/control_plane/service.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/control_plane/bot_operation_dispatcher.ex:22— `dispatcher_config().enabled and Process.whereis(@name)` appears character-identically in 5 files — elixir/threadr/lib/threadr/control_plane/bot_operation_dispatcher.ex, elixir/threadr/lib/threadr/control_plane/tenant_migration_dispatcher.ex, elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review_dispatcher.ex, elixir/threadr/lib/threadr/tenant_data/conversation_relationship_dispatcher.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:609— `entry[:entity_name] || entry["entity_name"]` appears character-identically in 3 files — elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex, elixir/threadr/lib/threadr_web/live/tenant_history_live/index.ex, elixir/threadr/lib/threadr_web/live/tenant_qa_live/index.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex:610— `entry[:entity_type] || entry["entity_type"]` appears character-identically in 3 files — elixir/threadr/lib/threadr_web/live/tenant_dossier_live/show.ex, elixir/threadr/lib/threadr_web/live/tenant_history_live/index.ex, elixir/threadr/lib/threadr_web/live/tenant_qa_live/index.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review.ex:23— `is_binary(conversation_id) and is_binary(tenant_schema)` appears character-identically in 2 files — elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review.ex, elixir/threadr/lib/threadr/tenant_data/conversation_relationship_recompute.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/tenant_data/conversation_attachment.ex:25— `is_binary(message_id) and is_binary(tenant_schema)` appears character-identically in 3 files — elixir/threadr/lib/threadr/tenant_data/conversation_attachment.ex, elixir/threadr/lib/threadr/tenant_data/graph.ex, elixir/threadr/lib/threadr/tenant_data/message_link_inference.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review.ex:34— `is_binary(tenant_schema) and is_integer(limit) and limit > 0` appears character-identically in 3 files — elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review.ex, elixir/threadr/lib/threadr/tenant_data/conversation_relationship_recompute.ex, elixir/threadr/lib/threadr/tenant_data/conversation_summarizer.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/ml/actor_qa.ex:22— `is_binary(tenant_subject_name) and is_binary(question)` appears character-identically in 7 files — elixir/threadr/lib/threadr/ml/actor_qa.ex, elixir/threadr/lib/threadr/ml/constrained_qa.ex, elixir/threadr/lib/threadr/ml/conversation_qa.ex, elixir/threadr/lib/threadr/ml/conversation_summary_qa.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review_dispatcher.ex:72— `is_integer(batch_size) and batch_size > 0` appears character-identically in 3 files — elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review_dispatcher.ex, elixir/threadr/lib/threadr/tenant_data/conversation_relationship_dispatcher.ex, elixir/threadr/lib/threadr/tenant_data/conversation_summary_dispatcher.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr_web/controllers/api/v1/dossier_controller.ex:161— `is_integer(value) or is_float(value) or is_boolean(value) or is_nil(value)` appears character-identically in 3 files — elixir/threadr/lib/threadr_web/controllers/api/v1/dossier_controller.ex, elixir/threadr/lib/threadr_web/controllers/api/v1/history_controller.ex, elixir/threadr/lib/threadr_web/controllers/api/v1/qa_controller.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/mix/tasks/threadr.smoke.discord_message.ex:334— `is_nil(token) or String.trim(token) == ""` appears character-identically in 2 files — elixir/threadr/lib/mix/tasks/threadr.smoke.discord_message.ex, elixir/threadr/lib/threadr/ingest/discord/bot.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/ml/generation/anthropic_provider.ex:49— `request.system_prompt || config[:system_prompt]` appears character-identically in 3 files — elixir/threadr/lib/threadr/ml/generation/anthropic_provider.ex, elixir/threadr/lib/threadr/ml/generation/chat_completions_provider.ex, elixir/threadr/lib/threadr/ml/generation/gemini_provider.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review_dispatcher.ex:113— `tenant.status == "active" and tenant.tenant_migration_status == "succeeded" and is_integer(tenant.tenant_migration_version) and tenant.tenan…` appears character-identically in 3 files — elixir/threadr/lib/threadr/tenant_data/conversation_cluster_review_dispatcher.ex, elixir/threadr/lib/threadr/tenant_data/conversation_relationship_dispatcher.ex, elixir/threadr/lib/threadr/tenant_data/conversation_summary_dispatcher.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate pkg/api/middleware/admin_auth.go:49— `!hasInstanceId || instanceId != expectedInstanceId` appears character-identically in 2 files — pkg/api/middleware/admin_auth.go, pkg/api/middleware/instance.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:607— `!node || node.details?.type === "cluster"` appears character-identically in 2 files — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js, elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js:586— `node.kind === "channel" || node.kind === "conversation"` appears character-identically in 2 files — elixir/threadr/assets/js/lib/threadr_graph/rendering_graph_methods.js, elixir/threadr/assets/js/lib/threadr_graph/rendering_selection_methods.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
README/code drift README.md:19— README.md links to `/Users/mfreeman/src/threadr/elixir/threadr`, but `Users/mfreeman/src/threadr/elixir/threadr` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:43— README.md links to `/Users/mfreeman/src/threadr/k8s/threadr`, but `Users/mfreeman/src/threadr/k8s/threadr` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:44— README.md links to `/Users/mfreeman/src/threadr/openspec`, but `Users/mfreeman/src/threadr/openspec` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:45— README.md links to `/Users/mfreeman/src/threadr/cmd`, but `Users/mfreeman/src/threadr/cmd` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:51— README.md links to `/Users/mfreeman/src/threadr/elixir/threadr/README.md`, but `Users/mfreeman/src/threadr/elixir/threadr/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:48— elixir/threadr/README.md names `threadr/cnpg-app`, but no file or folder `threadr/cnpg-app` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:128— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/control-plane/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/control-plane/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:154— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/production/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/production/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:178— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/nginx-tls/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/nginx-tls/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:180— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/prometheus-servicemonitor/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/prometheus-servicemonitor/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:182— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/restricted-network/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/restricted-network/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:193— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/bot-operator/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/bot-operator/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:222— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/REDACTED#L1`, but `Users/mfreeman/src/threadr/REDACTED` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:224— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/ghcr/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/control-plane/ghcr/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:249— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/REDACTED#L1`, but `Users/mfreeman/src/threadr/REDACTED` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:254— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/control-plane/application.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/control-plane/application.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:266— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/worker/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/worker/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:268— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/overlays/worker/production/kustomization.yaml#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/overlays/worker/production/kustomization.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:284— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/threadr/control-plane/seal_control_plane_env.sh#L1`, but `Users/mfreeman/src/threadr/k8s/threadr/control-plane/seal_control_plane_env.sh` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:331— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/REDACTED#L1`, but `Users/mfreeman/src/threadr/REDACTED` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift elixir/threadr/README.md:525— elixir/threadr/README.md links to `/Users/mfreeman/src/threadr/k8s/operators/ircbot-operator/config/crd/bases/cache.threadr.ai_threadrbots.yaml`, but `Users/mfreeman/src/threadr/k8s/operators/ircbot-operator/config/crd/bases/cache.threadr.ai_threadrbots.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file elixir/threadr/lib/threadr/control_plane/service.ex:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file elixir/threadr/lib/threadr_web/live/tenant_qa_live/index.ex:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file elixir/threadr/lib/threadr/ml/constrained_qa.ex:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
Dormant codebase — 119 of 119 significant files have no living knowledge — the codebase as a whole is dormant, not 119 separate risks. Counted over 119 of the 287 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
No runtime threat detection — No runtime threat-detection engine (Tetragon TracingPolicy / Falco) is committed. These observe process, file and network activity in-kernel and can alert or kill on malicious behaviour a static scan cannot catch.
D42 · Runtime Threat Enforcement· No admission-control policy · ×1
No admission-control policy — No policy-enforcement gate (Kyverno / OPA Gatekeeper / PodSecurity admission) is committed. Admission control keeps workloads that violate your security baseline from ever reaching the cluster.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No app-layer HTTPS enforcement detected — This repository runs an HTTP server and nothing in its Elixir source or production configuration secures the transport: no HTTPS served (an endpoint's `https: [...]`, `scheme: :https`, `Plug.Cowboy.https`, SiteEncrypt), no `force_ssl:` or `plug Plug.SSL` redirecting to HTTPS and sending HSTS, no `strict-transport-security` header, no `rewrite_on: [:x_forwarded_proto]` or `x-forwarded-proto` read for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: elixir/threadr/lib/threadr/control_plane/smoke_server.ex:63 — `Bandit`.
Security headers incomplete — Set: Content-Security-Policy, Referrer-Policy, X-Content-Type-Options, X-Permitted-Cross-Domain-Policies. Missing: Strict-Transport-Security, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.0 on this card.) The server: elixir/threadr/lib/threadr/control_plane/smoke_server.ex:63 — `Bandit`.
X2 · Cancellation propagation· Not all functions that make a request accept a context.Context or an AbortSignal · ×1
Not all functions that make a request accept a context.Context or an AbortSignal — Only 3/7 functions that make a cancellable request (fetch, axios, ky, ofetch; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Outdated: ash — `:ash` is locked at 3.19.3 but 3.37.0 is the current stable release on hex.pm, and it already satisfies the `"~> 3.19"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ash` and commit the updated REDACTED.
Outdated: ash_authentication — `:ash_authentication` is locked at 4.13.7 but 4.15.0 is the current stable release on hex.pm, and it already satisfies the `"~> 4.13"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ash_authentication` and commit the updated REDACTED.
Outdated: ash_authentication_phoenix — `:ash_authentication_phoenix` is locked at 2.15.0 but 2.17.4 is the current stable release on hex.pm, and it already satisfies the `"~> 2.15"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ash_authentication_phoenix` and commit the updated REDACTED.
Outdated: ash_phoenix — `:ash_phoenix` is locked at 2.3.20 but 2.3.25 is the current stable release on hex.pm, and it already satisfies the `"~> 2.3"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ash_phoenix` and commit the updated REDACTED.
Outdated: ash_postgres — `:ash_postgres` is locked at 2.6.32 but 2.15.1 is the current stable release on hex.pm, and it already satisfies the `"~> 2.6"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ash_postgres` and commit the updated REDACTED.
Outdated: ash_state_machine — `:ash_state_machine` is locked at 0.2.12 but 0.2.13 is the current stable release on hex.pm, and it already satisfies the `"~> 0.2"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ash_state_machine` and commit the updated REDACTED.
Outdated: bandit — `:bandit` is locked at 1.10.3 but 1.13.1 is the current stable release on hex.pm, and it already satisfies the `"~> 1.5"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update bandit` and commit the updated REDACTED.
Outdated: broadway — `:broadway` is locked at 1.2.1 but 1.3.0 is the current stable release on hex.pm, and it already satisfies the `"~> 1.2"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update broadway` and commit the updated REDACTED.
Outdated: ecto_sql — `:ecto_sql` is locked at 3.13.5 but 3.14.0 is the current stable release on hex.pm, and it already satisfies the `"~> 3.13"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ecto_sql` and commit the updated REDACTED.
Outdated: esbuild — `:esbuild` is locked at 0.10.0 but 0.10.1 is the current stable release on hex.pm, and it already satisfies the `"~> 0.10"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update esbuild` and commit the updated REDACTED.
Outdated: gnat — `:gnat` is locked at 1.13.0 but 1.18.1 is the current stable release on hex.pm, and it already satisfies the `"~> 1.13"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update gnat` and commit the updated REDACTED.
Outdated: jason — `:jason` is locked at 1.4.4 but 1.4.5 is the current stable release on hex.pm, and it already satisfies the `"~> 1.2"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update jason` and commit the updated REDACTED.
Outdated: lazy_html — `:lazy_html` is locked at 0.1.10 but 0.1.13 is the current stable release on hex.pm, and it already satisfies the `">= 0.1.0"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update lazy_html` and commit the updated REDACTED.
Outdated: phoenix — `:phoenix` is locked at 1.8.5 but 1.8.16 is the current stable release on hex.pm, and it already satisfies the `"~> 1.8.1"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update phoenix` and commit the updated REDACTED.
Outdated: phoenix_live_reload — `:phoenix_live_reload` is locked at 1.6.2 but 1.7.0 is the current stable release on hex.pm, and it already satisfies the `"~> 1.2"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update phoenix_live_reload` and commit the updated REDACTED.
Outdated: postgrex — `:postgrex` is locked at 0.22.0 but 0.22.4 is the current stable release on hex.pm, and it already satisfies the `">= 0.0.0"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update postgrex` and commit the updated REDACTED.
Outdated: req — `:req` is locked at 0.5.17 but 0.7.5 is the current stable release on hex.pm, and it already satisfies the `"~> 0.5"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update req` and commit the updated REDACTED.
Outdated: rustler — `:rustler` is locked at 0.37.3 but 0.38.0 is the current stable release on hex.pm, and it already satisfies the `"~> 0.37"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update rustler` and commit the updated REDACTED.
Outdated: swoosh — `:swoosh` is locked at 1.23.0 but 1.29.0 is the current stable release on hex.pm, and it already satisfies the `"~> 1.16"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update swoosh` and commit the updated REDACTED.
Outdated: tailwind — `:tailwind` is locked at 0.4.1 but 0.5.1 is the current stable release on hex.pm, and it already satisfies the `"~> 0.3"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update tailwind` and commit the updated REDACTED.
Outdated: telemetry_metrics — `:telemetry_metrics` is locked at 1.1.0 but 1.2.0 is the current stable release on hex.pm, and it already satisfies the `"~> 1.0"` requirement declared in elixir/threadr/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update telemetry_metrics` and commit the updated REDACTED.
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.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
Run 01a16489-74c9-79c1-b030-0e283970da45 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 86 · Warnings: 939 · Recommendations: 367 · Info: 21 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 16:54 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.