Public report of eigr/spawn, 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:33 UTC · Survey ID cd_0ce5c9f04536426c8652d6458555a6fb
eigr/spawn
Measured 22 October 2026, 17:26 UTC, at code version d2c3a55
CAI scoreAt riskDown 6 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: 28,043 lines of product code in 13 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 31
Findings by how serious they are
144 critical324 serious120 minor
25 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, 17:26 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 ▸
47of 51 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.
510of 588 findings point to an exact file and line, so you can open each one in the code. The other 78 concern the repository as a whole, such as missing documentation.
51dimensions across 6 lenses, read from 28,043 lines of product code in 13 projects.
eigr/spawn scores 44 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 Production Readiness, which scores 31 and is rated Weak. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 8 Leaked secret finding(s) in REDACTED Scanning and to resolve the 2 Unbounded dependency requirement finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 44 to about 53.
144 findings are critical: 42 in Static Analysis (SAST), 30 in Change Coupling, 30 in IaC & Container Security, 29 in Dependency Vulnerabilities, eight in REDACTED Scanning, four in Secrets (history) and one in Web-Security Posture.
Watchdog couldn't measure 25 dimensions in this code, among them Code Coverage, Test Reliability and License Compliance, so they are left out of the score. The product code is 28,043 lines, which would take an estimated 0.2 person-years, around €29,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.
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: 2 findings
These 2 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one.
IaC & Container Security · Medium IaC: CKV_K8S_19 REDACTED
Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €29,000 · Estimate
Cost to rebuild
€9,500 to €48,000, for 159 to 504 hours of work, about 0.2 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 44. 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: 28,043 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 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED (2).
Raises the score by about 12 points · Low effort · REDACTED Scanning
2
Resolve the 2 Unbounded dependency requirement finding(s) in Dependency Hygiene.
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 5 points · Low effort · ADR Quality
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 €29,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 31 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 8 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 12 points for low effort, because it clears the 8 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 — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
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.
136 modules, with 30 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; 96 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.
Actors.Actor.Interface uses Actors.Actor, so a change to Actors.Actor can break Actors.Actor.Interface, while a change to Actors.Actor.Interface can't break Actors.Actor.
Position
Below the diagonal: Actors.Actor.Interface uses a module listed above it, which is the healthy direction.
Actors.Registry.LoadBalance.Strategies uses Actors.Registry.LoadBalance, so a change to Actors.Registry.LoadBalance can break Actors.Registry.LoadBalance.Strategies, while a change to Actors.Registry.LoadBalance.Strategies can't break Actors.Registry.LoadBalance.
Position
Below the diagonal: Actors.Registry.LoadBalance.Strategies uses a module listed above it, which is the healthy direction.
Actors.Security.Acl uses Actors.Security, so a change to Actors.Security can break Actors.Security.Acl, while a change to Actors.Security.Acl can't break Actors.Security.
Position
Below the diagonal: Actors.Security.Acl uses a module listed above it, which is the healthy direction.
Spawn.Cluster.Provisioner.Executor.Spawn.Cluster.Provisioner uses Spawn.Cluster.Provisioner, so a change to Spawn.Cluster.Provisioner can break Spawn.Cluster.Provisioner.Executor.Spawn.Cluster.Provisioner, while a change to Spawn.Cluster.Provisioner.Executor.Spawn.Cluster.Provisioner can't break Spawn.Cluster.Provisioner.
Position
Below the diagonal: Spawn.Cluster.Provisioner.Executor.Spawn.Cluster.Provisioner uses a module listed above it, which is the healthy direction.
Spawn.Cluster.StateHandoff.Controllers uses Spawn.Cluster.StateHandoff, so a change to Spawn.Cluster.StateHandoff can break Spawn.Cluster.StateHandoff.Controllers, while a change to Spawn.Cluster.StateHandoff.Controllers can't break Spawn.Cluster.StateHandoff.
Position
Below the diagonal: Spawn.Cluster.StateHandoff.Controllers uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in SpawnCtl.Commands.Install.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.K8sRuntime uses a type in SpawnCtl.Commands.Install.Behavior.
SpawnCtl.Commands.Install.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.K8sRuntime uses SpawnCtl.Commands.Install.Behavior, so a change to SpawnCtl.Commands.Install.Behavior can break SpawnCtl.Commands.Install.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.K8sRuntime, while a change to SpawnCtl.Commands.Install.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.K8sRuntime can't break SpawnCtl.Commands.Install.Behavior.
Position
Below the diagonal: SpawnCtl.Commands.Install.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.K8sRuntime uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in SpawnCtl.Commands.New.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.UnixRuntime uses a type in SpawnCtl.Commands.New.Behavior.
SpawnCtl.Commands.New.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.UnixRuntime uses SpawnCtl.Commands.New.Behavior, so a change to SpawnCtl.Commands.New.Behavior can break SpawnCtl.Commands.New.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.UnixRuntime, while a change to SpawnCtl.Commands.New.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.UnixRuntime can't break SpawnCtl.Commands.New.Behavior.
Position
Below the diagonal: SpawnCtl.Commands.New.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.UnixRuntime uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in SpawnCtl.Commands.New.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.WindowsRuntime uses a type in SpawnCtl.Commands.New.Behavior.
SpawnCtl.Commands.New.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.WindowsRuntime uses SpawnCtl.Commands.New.Behavior, so a change to SpawnCtl.Commands.New.Behavior can break SpawnCtl.Commands.New.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.WindowsRuntime, while a change to SpawnCtl.Commands.New.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.WindowsRuntime can't break SpawnCtl.Commands.New.Behavior.
Position
Below the diagonal: SpawnCtl.Commands.New.Behavior.Runtime.Spawnctl.Runtimes.Behaviors.WindowsRuntime uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.Activators.Api uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.Activators.Api, while a change to SpawnOperator.K8s.Activators.Api can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.Activators.Api uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.Activators.Api.Cm uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.Activators.Api.Cm, while a change to SpawnOperator.K8s.Activators.Api.Cm can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.Activators.Api.Cm uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.Activators.Rabbitmq uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.Activators.Rabbitmq, while a change to SpawnOperator.K8s.Activators.Rabbitmq can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.Activators.Rabbitmq uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.Activators.Rabbitmq.Cm uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.Activators.Rabbitmq.Cm, while a change to SpawnOperator.K8s.Activators.Rabbitmq.Cm can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.Activators.Rabbitmq.Cm uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.Activators.Scheduler uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.Activators.Scheduler, while a change to SpawnOperator.K8s.Activators.Scheduler can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.Activators.Scheduler uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.Activators.Scheduler.Cm uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.Activators.Scheduler.Cm, while a change to SpawnOperator.K8s.Activators.Scheduler.Cm can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.Activators.Scheduler.Cm uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.Plugins uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.Plugins, while a change to SpawnOperator.K8s.Plugins can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.Plugins uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.Proxy uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.Proxy, while a change to SpawnOperator.K8s.Proxy can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.Proxy uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.Proxy.CM uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.Proxy.CM, while a change to SpawnOperator.K8s.Proxy.CM can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.Proxy.CM uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.System uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.System, while a change to SpawnOperator.K8s.System can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.System uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.System.Secret uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.System.Secret, while a change to SpawnOperator.K8s.System.Secret can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.System.Secret uses a module listed above it, which is the healthy direction.
SpawnOperator.K8s.System.Secret.CertManager uses SpawnOperator.K8s, so a change to SpawnOperator.K8s can break SpawnOperator.K8s.System.Secret.CertManager, while a change to SpawnOperator.K8s.System.Secret.CertManager can't break SpawnOperator.K8s.
Position
Below the diagonal: SpawnOperator.K8s.System.Secret.CertManager uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.K3d uses a type in Spawnctl.Commands.Playground.K8s.Behavior.
Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.K3d uses Spawnctl.Commands.Playground.K8s.Behavior, so a change to Spawnctl.Commands.Playground.K8s.Behavior can break Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.K3d, while a change to Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.K3d can't break Spawnctl.Commands.Playground.K8s.Behavior.
Position
Below the diagonal: Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.K3d uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.Kind uses a type in Spawnctl.Commands.Playground.K8s.Behavior.
Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.Kind uses Spawnctl.Commands.Playground.K8s.Behavior, so a change to Spawnctl.Commands.Playground.K8s.Behavior can break Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.Kind, while a change to Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.Kind can't break Spawnctl.Commands.Playground.K8s.Behavior.
Position
Below the diagonal: Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.Kind uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.Minikube uses a type in Spawnctl.Commands.Playground.K8s.Behavior.
Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.Minikube uses Spawnctl.Commands.Playground.K8s.Behavior, so a change to Spawnctl.Commands.Playground.K8s.Behavior can break Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.Minikube, while a change to Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.Minikube can't break Spawnctl.Commands.Playground.K8s.Behavior.
Position
Below the diagonal: Spawnctl.Commands.Playground.K8s.Behavior.Installer.Spawnctl.Commands.Playground.K8s.Minikube uses a module listed above it, which is the healthy direction.
SpawnSdkExample.Actors uses SpawnSdk, so a change to SpawnSdk can break SpawnSdkExample.Actors, while a change to SpawnSdkExample.Actors can't break SpawnSdk.
Position
Below the diagonal: SpawnSdkExample.Actors uses a module listed above it, which is the healthy direction.
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
152
High / Critical
A03:2025 — Software Supply Chain Failures
49
High / Critical
A05:2025 — Injection
47
High / Critical
A07:2025 — Authentication Failures
13
High / Critical
Roadmap
First, resolve the eight leaked secrets in test and development configuration files to secure sensitive credentials. Next, harden the web-security posture by enabling strict TLS certificate verification and removing insecure overrides to ensure proper chain validation. Then, address the two unbounded dependency requirements to stabilize the build environment, and establish architectural decision records to document key technical choices. Finally, update the documentation to accurately reflect the current single-project structure and fix broken internal links.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED (2).
Stop accepting every TLS certificate: delete `verify: :verify_none` (hackney's `insecure: true`, a `verify_fun` that answers `{:valid, _}`, a `match_fun` that returns `true`) so the chain, hostname and expiry are verified, and trust a self-signed or private server by giving the client its CA (`cacertfile:`, `cacerts:`) — never by switching verification off.
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; docs/local_development.md links to `CONTRIBUTING.md`, but `docs/CONTRIBUTING.md` does not exist; docs/overview.md links to `docs/index.md`, but `docs/docs/index.md` does not exist; docs/overview.md links to `docs/getting_started.md`, but `docs/docs/getting_started.md` does not exist; docs/statestores.md links to `docs/getting_started.md`, but `docs/docs/getting_started.md` does not exist.
Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
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 — 144
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 — 324
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 — 120
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 25
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. 47 of 51 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 — 51 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, 510 of 588 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, .ex) 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, .ex) 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 — 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. Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (an Elixir mix.exs/REDACTED (Hex)), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
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 (11 contributor(s) across 2481 commit(s) sampled, automation and bot accounts excluded). One of them holds 83% of the history; the other 10 hold 1.7% 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 (mix.exs), 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.
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) — nats Pulling otel Pulling adminer Pulling zipkin Pulling mysql Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden adminer Error context canceled otel Error context canceled mysql Error context canceled mariadb Error context canceled nats Error context canceled zipkin Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: mysql Error Get "https://registry-1.docker.io/v2/": Forbidden mariadb Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error context canceled nats Error Get "https://registry-1.docker.io/v2/": Forbidden zipkin Error context canceled adminer 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 no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Elixir, Go 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 no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Elixir, Go 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.
X1 Async correctness — 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 JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — 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 JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — 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 JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — 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 JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — 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 JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — 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 JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — 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 JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — 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 JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — 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 Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Go 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.
X23 Unguarded diagnostic materialisation — 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 JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — 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 JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — 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 JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — 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 Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Elixir, Go 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.
X29 Per-element action decided by a fixed element — 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 JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — 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 JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
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").
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.
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.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, 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.
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.
Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with CallerConsumer.invoke_with_span (cognitive 19), StateManager.save_async (cognitive 16). — 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 2 together lifts Cognitive Complexity from 9.6 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 Classes8.8 / 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 7 FileTooLong finding(s) in God Classes — start with protocol.pb.ex, actor.pb.ex, persistent_term_config.ex. — One of this dimension's main actionable groups (7 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.
148 duplicated block group(s) detected. A further 15 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 25 of the 163 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 116 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with actor.pb.ex, api.ex, mariadb_projection_adapter.ex. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with healthcheck.pb.ex, actor_system_handler.ex, mariadb_projection_adapter.ex. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with initializer.ex, dispatcher.ex, actor_invoker_generator.ex. — One of this dimension's main actionable groups (4 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 · Coupling9.4 / 10Stronggated by 1 serious finding✓ 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.
13 production modules (Go+OTP), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
Off the main sequence: spawn_statestores
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
54 outdated, 1 retired direct Hex dependencies, 2 pinning defect(s). 89 of 99 direct dependencies were graded against hex.pm (0 not published there, 10 not resolved by a committed lockfile). 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.
Unbounded dependency requirement: bakeware · ×2
Retired release: jetstream
Outdated: bandit · ×54
What to do
Resolve the 2 Unbounded dependency requirement finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Retired release 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 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 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: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: 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.
14 deducted task-comment markers across 28043 LoC (0.0/KLoC) → score 9.9. 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 14 TodoComment finding(s) in Explicit Debt — start with nats.ex (3), actor_host_handler.ex (2), invocation.ex. — One of this dimension's main actionable groups (14 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 gives a strong overview (Spawn actor-native service mesh for durable stateful computing) and links to the website/blog, while its spawn_sdk/spawn_sdk_example/README.md provides installation and usage. The architecture document is excellent at describing the Eigr Functions Spawn platform components (k8s Operator, Cloud Storage, Activators, Actor Host Function), with a diagram. However, most README files are for subdirectories rather than the repository root, so the overview/installation/usage/contribution guidance resides in the root README and must be judged there. The Spawn CLI documentation is clear and complete for a command-line tool — it opens with an overview of the project (spawn new, apply, config, dev, install, playground) and its subcommands, then dives into each one with detailed descriptions, usage examples, options, and subcommand breakdowns. The conceptual document explains what Spawn is, its goals, the sidecar proxy pattern, BEAM/OTP stack, and a list of components (stateful serverless platform, Inversion of State, polyglot), before clipping mid-sentence. A dedicated contribution guide exists but is stubbed ('TODO').
What to do
Improve Documentation Quality — currently 8.2/10. — The repository's root README gives a strong overview (Spawn actor-native service mesh for durable stateful computing) and links to the website/blog, while its spawn_sdk/spawn_sdk_example/README.md provides installation and usage. The architecture document is excellent at describing the Eigr Functions Spawn platform components (k8s Operator, Cloud Storage, Activators, Actor Host Function), with a diagram. However, most README files are for subdirectories rather than the repository root, so the overview/installation/usage/contribution guidance resides in the root README and must be judged there. The Spawn CLI documentation is clear and complete for a command-line tool — it opens with an overview of the project (spawn new, apply, config, dev, install, playground) and its subcommands, then dives into each one with detailed descriptions, usage examples, options, and subcommand breakdowns. The conceptual document explains what Spawn is, its goals, the sidecar proxy pattern, BEAM/OTP stack, and a list of components (stateful serverless platform, Inversion of State, polyglot), before clipping mid-sentence. A dedicated contribution guide exists but is stubbed ('TODO').
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.
1 of 13 build units (Go, Mix) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: 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.
4 finding(s): 0 critical, 4 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 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).
47 finding(s): 0 critical, 42 high, 5 medium, 0 low. 23 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9). — One of this dimension's main actionable groups (9 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 23 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 (23 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 26 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (26). — One of this dimension's main actionable groups (26 issue-level).
Resolve the 11 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10), REDACTED. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 100 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (27), REDACTED (22), REDACTED (21). — One of this dimension's main actionable groups (100 warning-level).
Resolve the 18 High IaC finding(s) in IaC & Container Security — start with REDACTED (7), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (18 issue-level).
Resolve the 12 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED. — One of this dimension's main actionable groups (12 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.
7 of 82 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex. Counted over 82 of the 302 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
Resolve the 30 Boundary-crossing change coupling finding(s) in Change Coupling — start with initializer.ex (14), internal_versions.exs (7), mix.exs (6). — One of this dimension's main actionable groups (30 issue-level).
Resolve the 6 Change coupling finding(s) in Change Coupling — start with spawn_operator.ex, initializer.ex, actor_host_handler.ex. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with config.exs, customizer.ex, deployment.ex. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0/4 workload(s) run every container under a seccomp profile; 0/4 declare an AppArmor/SELinux profile.
No seccomp profile · ×4REDACTED:2
What to do
Resolve the 4 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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 4 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.
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 singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
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?
C2 · Access Controls4.7 / 10Weak✓ 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.
Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
What to do
Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
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.
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 advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:226
docs/local_development.md links to `CONTRIBUTING.md`, but `docs/CONTRIBUTING.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. — docs/local_development.md:17
docs/overview.md links to `docs/index.md`, but `docs/docs/index.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. — docs/overview.md:9
docs/overview.md links to `docs/getting_started.md`, but `docs/docs/getting_started.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. — docs/overview.md:9
docs/statestores.md links to `docs/getting_started.md`, but `docs/docs/getting_started.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. — docs/statestores.md:4
tools/sdk-init/README.md documents the environment variable `GOOS`, but no code, script or configuration file names it. 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. — tools/sdk-init/README.md:63
tools/sdk-init/README.md documents the environment variable `GOARCH`, but no code, script or configuration file names it. 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. — tools/sdk-init/README.md:63
tools/sdk-init/README.md documents the environment variable `CGO_ENABLED`, but no code, script or configuration file names it. 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. — tools/sdk-init/README.md:63
What to do
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; docs/local_development.md links to `CONTRIBUTING.md`, but `docs/CONTRIBUTING.md` does not exist; docs/overview.md links to `docs/index.md`, but `docs/docs/index.md` does not exist; docs/overview.md links to `docs/getting_started.md`, but `docs/docs/getting_started.md` does not exist; docs/statestores.md links to `docs/getting_started.md`, but `docs/docs/getting_started.md` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Only 10/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `spawnctl`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.
No static application security testing detected. For this repository's stack, add sobelow (Elixir/Phoenix) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 10879 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: sobelow (Elixir/Phoenix) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `github-actions`, `gomod` — add those `package-ecosystem` entries to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ 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.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not 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.get(` 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. (×3) — spawnctl/lib/spawnctl/readme_fetcher.ex:12, spawnctl/lib/spawnctl/runtimes/behaviors/k8s_runtime.ex:47, spawnctl/lib/spawnctl/runtimes/behaviors/unix_runtime.ex:53
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.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
A Elixir Benchee/Benchfella suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — spawn_sdk/spawn_sdk_example/benchmark.exs
What to do
Give Benchee a `memory_time:` (e.g. `memory_time: 2`) so each job's memory usage is measured beside its run time and allocation regressions are visible.
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 (spawn_monitor/lib/spawn_monitor_web/endpoint.ex:3 — `Phoenix.Endpoint`), 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.
`verify: :verify_none` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the peer is verified — `verify: :verify_peer` is what `:ssl`, Mint, Finch, Req and hackney use when nothing is set (OTP 26 and later default to it). Give it the trust roots to check against: `cacerts: :public_key.cacerts_get()` (OTP 25+) or the `CAStore` package's `cacertfile: CAStore.file_path()`, with `customize_hostname_check: [match_fun: :public_key.pkix_verify_hostname_match_fun(:https)]` so the hostname is checked too. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `cacertfile:`/`cacerts:`, which keeps the chain and hostname checks on. — spawn_statestores/statestores/lib/statestores/util.ex:184
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: spawn_monitor/lib/spawn_monitor_web/endpoint.ex:3 — `Phoenix.Endpoint`.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Elixir server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: spawn_monitor/lib/spawn_monitor_web/endpoint.ex:3 — `Phoenix.Endpoint`.
What to do
Stop accepting every TLS certificate: delete `verify: :verify_none` (hackney's `insecure: true`, a `verify_fun` that answers `{:valid, _}`, a `match_fun` that returns `true`) so the chain, hostname and expiry are verified, and trust a self-signed or private server by giving the client its CA (`cacertfile:`, `cacerts:`) — never by switching verification off.
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: …]`.
Set security response headers on what the server sends — keep `plug :put_secure_browser_headers` in the router's `:browser` pipeline (pass a `%{"content-security-policy" => …}` map to add a policy), and for a Plug or API pipeline add a plug that calls `put_resp_header(conn, "x-content-type-options", "nosniff")` and sets a content-security-policy and frame policy.
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 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?
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.
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?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 1 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.
X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 68 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — 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.
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) — nats Pulling otel Pulling adminer Pulling zipkin Pulling mysql Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden adminer Error context canceled otel Error context canceled mysql Error context canceled mariadb Error context canceled nats Error context canceled zipkin Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: mysql Error Get "https://registry-1.docker.io/v2/": Forbidden mariadb Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error context canceled nats Error Get "https://registry-1.docker.io/v2/": Forbidden zipkin Error context canceled adminer 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.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (an Ecto repo, Postgrex, MyXQL, Exqlite, Mongo, Mnesia, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (Ecto, Postgrex, MyXQL, Mongo, EventStore, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (an Ecto repo, Postgrex, MyXQL, Exqlite, Mongo, Mnesia, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (an Ecto repo, Postgrex, MyXQL, Exqlite, Mongo, Mnesia, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~4840 lines of test source are present (.exs, .ex) 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
D14 License Compliance — Package manifest not parsed for licence data — analyzer language-coverage gap
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.
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
D9 Test Distribution — Test source is present (.exs, .ex) 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 12 value object(s)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby 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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
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
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 118 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
PF3 Async & latency hygiene — Not applicable: Elixir and Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
X1 Async correctness — 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
X12 Unreachable branch — 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
X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X16 Unfloored truncation loop — not 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
X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X18 Disposal-pattern correctness — not 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
X19 Unrestored process-global state — 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
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. An Elixir guard admits only guard-safe expressions — the compiler rejects anything else — and a bound value is never mutated in place. Go's `++`, `--` and assignments are STATEMENTS, not expressions, so none of them can appear in a `case` expression or anywhere else in a condition, and a type switch's cases are types. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — 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
X23 Unguarded diagnostic materialisation — 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
X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X25 Inert configuration knob — not 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
X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X29 Per-element action decided by a fixed element — 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
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 — 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
X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Elixir's `nil` is an atom in a dynamically typed language: `@spec`s are checked by an external analysis that has no nullability operator, so there is no null-typed discipline in the language to adopt. Go's type system has no nullable and non-nullable types — every pointer, map, slice and interface is nil-able at every position, there is no switch that turns null checking on, and the compiler produces no nullability warning for an operator to silence. Not a gap in the analyzer and not a finding about your code.
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.
Boundary-crossing change coupling: initializer.ex ↔ deployment.ex spawn_initializer/lib/spawn_initializer/tls/initializer.ex:1— `spawn_initializer/lib/spawn_initializer/tls/initializer.ex` (context spawn_initializer) and `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 97% of the time (32 of the 33 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 32 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ customizer.ex spawn_initializer/lib/spawn_initializer/tls/initializer.ex:1— `spawn_initializer/lib/spawn_initializer/tls/initializer.ex` (context spawn_initializer) and `spawn_operator/spawn_operator/lib/mix/tasks/bonny.gen.manifest/customizer.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 94% of the time (31 of the 33 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ sidecar_configmap.ex spawn_initializer/lib/spawn_initializer/tls/initializer.ex:1— `spawn_initializer/lib/spawn_initializer/tls/initializer.ex` (context spawn_initializer) and `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/configmap/sidecar_configmap.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 94% of the time (31 of the 33 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ actor_host_handler.ex spawn_initializer/lib/spawn_initializer/tls/initializer.ex:1— `spawn_initializer/lib/spawn_initializer/tls/initializer.ex` (context spawn_initializer) and `spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_host_handler.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 94% of the time (31 of the 33 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ spawn_operator.ex spawn_initializer/lib/spawn_initializer/tls/initializer.ex:1— `spawn_initializer/lib/spawn_initializer/tls/initializer.ex` (context spawn_initializer) and `spawn_operator/spawn_operator/lib/spawn_operator.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 94% of the time (31 of the 33 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ config.exs spawn_initializer/lib/spawn_initializer/tls/initializer.ex:1— `spawn_initializer/lib/spawn_initializer/tls/initializer.ex` (context spawn_initializer) and `spawn_operator/spawn_operator/config/config.exs` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 94% of the time (31 of the 33 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ deployment.ex lib/actors/security/tls/initializer.ex:1— `lib/actors/security/tls/initializer.ex` (context actors) and `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 89% of the time (32 of the 36 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 32 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ config.exs lib/actors/security/tls/initializer.ex:1— `lib/actors/security/tls/initializer.ex` (context actors) and `spawn_operator/spawn_operator/config/config.exs` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 86% of the time (31 of the 36 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ customizer.ex lib/actors/security/tls/initializer.ex:1— `lib/actors/security/tls/initializer.ex` (context actors) and `spawn_operator/spawn_operator/lib/mix/tasks/bonny.gen.manifest/customizer.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 86% of the time (31 of the 36 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ spawn_operator.ex lib/actors/security/tls/initializer.ex:1— `lib/actors/security/tls/initializer.ex` (context actors) and `spawn_operator/spawn_operator/lib/spawn_operator.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 86% of the time (31 of the 36 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ actor_host_handler.ex lib/actors/security/tls/initializer.ex:1— `lib/actors/security/tls/initializer.ex` (context actors) and `spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_host_handler.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 86% of the time (31 of the 36 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ sidecar_configmap.ex lib/actors/security/tls/initializer.ex:1— `lib/actors/security/tls/initializer.ex` (context actors) and `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/configmap/sidecar_configmap.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 86% of the time (31 of the 36 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: internal_versions.exs ↔ initializer.ex priv/internal_versions.exs:1— `priv/internal_versions.exs` (context priv) and `spawn_initializer/lib/spawn_initializer/tls/initializer.ex` (context spawn_initializer) sit in DIFFERENT parts of the tree yet change together 85% of the time (28 of the 33 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 28 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: mix.exs ↔ deployment.ex spawn_initializer/mix.exs:1— `spawn_initializer/mix.exs` (context spawn_initializer) and `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ internal_versions.exs lib/actors/security/tls/initializer.ex:1— `lib/actors/security/tls/initializer.ex` (context actors) and `priv/internal_versions.exs` (context priv) sit in DIFFERENT parts of the tree yet change together 78% of the time (28 of the 36 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 28 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: internal_versions.exs ↔ config.exs priv/internal_versions.exs:1— `priv/internal_versions.exs` (context priv) and `spawn_operator/spawn_operator/config/config.exs` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 73% of the time (36 of the 49 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 36 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: mix.exs ↔ sidecar_configmap.ex spawn_initializer/mix.exs:1— `spawn_initializer/mix.exs` (context spawn_initializer) and `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/configmap/sidecar_configmap.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: mix.exs ↔ spawn_operator.ex spawn_initializer/mix.exs:1— `spawn_initializer/mix.exs` (context spawn_initializer) and `spawn_operator/spawn_operator/lib/spawn_operator.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: mix.exs ↔ customizer.ex spawn_initializer/mix.exs:1— `spawn_initializer/mix.exs` (context spawn_initializer) and `spawn_operator/spawn_operator/lib/mix/tasks/bonny.gen.manifest/customizer.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: mix.exs ↔ config.exs spawn_initializer/mix.exs:1— `spawn_initializer/mix.exs` (context spawn_initializer) and `spawn_operator/spawn_operator/config/config.exs` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: internal_versions.exs ↔ mix.exs priv/internal_versions.exs:1— `priv/internal_versions.exs` (context priv) and `spawn_initializer/mix.exs` (context spawn_initializer) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: initializer.ex ↔ mix.exs lib/actors/security/tls/initializer.ex:1— `lib/actors/security/tls/initializer.ex` (context actors) and `spawn_initializer/mix.exs` (context spawn_initializer) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: caller_consumer.ex ↔ mix.exs lib/actors/actor/caller_consumer.ex:1— `lib/actors/actor/caller_consumer.ex` (context actors) and `spawn_initializer/mix.exs` (context spawn_initializer) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: mix.exs ↔ actor_host_handler.ex spawn_initializer/mix.exs:1— `spawn_initializer/mix.exs` (context spawn_initializer) and `spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_host_handler.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Boundary-crossing change coupling: internal_versions.exs ↔ customizer.ex priv/internal_versions.exs:1— `priv/internal_versions.exs` (context priv) and `spawn_operator/spawn_operator/lib/mix/tasks/bonny.gen.manifest/customizer.ex` (context spawn_operator) sit in DIFFERENT parts of the tree yet change together 65% of the time (33 of the 51 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 33 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
TLS certificate validation disabled spawn_statestores/statestores/lib/statestores/util.ex:184— `verify: :verify_none` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the peer is verified — `verify: :verify_peer` is what `:ssl`, Mint, Finch, Req and hackney use when nothing is set (OTP 26 and later default to it). Give it the trust roots to check against: `cacerts: :public_key.cacerts_get()` (OTP 25+) or the `CAStore` package's `cacertfile: CAStore.file_path()`, with `customize_hostname_check: [match_fun: :public_key.pkix_verify_hostname_match_fun(:https)]` so the hostname is checked too. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `cacertfile:`/`cacerts:`, which keeps the chain and hostname checks on.
TodoComment lib/actors/actor/entity/invocation.ex:553— # TODO: Validate state before invoke — 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 lib/spawn/cluster/cluster_supervisor.ex:29— # TODO check if is production env — 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 lib/spawn/utils/nats.ex:15— # TODO: Verify if necessary default value — 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 lib/spawn/utils/nats.ex:36— # TODO: Get other parameters here to build complex connections — 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 lib/spawn/utils/nats.ex:46— # TODO: Get other parameters here to build complex connections — 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 spawn_operator/spawn_operator/lib/spawn_operator/k8s_conn.ex:32— # TODO It is a workaround and needed to be removed — 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 spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_host_handler.ex:120— # TODO: Reconcile hpa for rebalancing Nodes — 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 spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_host_handler.ex:121— # TODO: Recreate resources if not exists — 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 spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/configmap/sidecar_configmap.ex:140— # TODO use secrets to storage nats configuration — 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 spawn_operator/spawn_operator/lib/spawn_operator/k8s/system/secret/actor_system_secret.ex:60— # TODO check if encryption key is necessary — 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 spawn_sdk/spawn_sdk/lib/actor.ex:298— # TODO: implement this in Proxy too? — 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 spawn_sdk/spawn_sdk_example/mix.exs:34— # TODO: Removing :spawn_statestores dependency — 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 spawn_statestores/statestores/lib/statestores/supervisor.ex:38— # TODO: migrate via job in production (future release) — 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 spawn_statestores/statestores_postgres/test/repo_test.exs:125— # TODO: The implementation should include the snapshot table when using get_all_snapshots... — 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×11
FileTooLong: actors/protocol.pb.ex lib/_generated/spawn/actors/protocol.pb.ex— FileTooLong — 1843 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1343 over it, 3.69× 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: actors/actor.pb.ex lib/_generated/spawn/actors/actor.pb.ex— FileTooLong — 1263 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 763 over it, 2.53× 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: config/persistent_term_config.ex lib/actors/config/persistent_term_config.ex— FileTooLong — 653 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 153 over it, 1.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: actors/healthcheck.pb.ex lib/_generated/spawn/actors/healthcheck.pb.ex— FileTooLong — 651 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 151 over it, 1.30× 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: entity/invocation.ex lib/actors/actor/entity/invocation.ex— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 124 over it, 1.25× 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: actor/caller_consumer.ex lib/actors/actor/caller_consumer.ex— FileTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 64 over it, 1.13× 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: system/spawn_system.ex spawn_sdk/spawn_sdk/lib/system/spawn_system.ex— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× 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.
Change coupling: spawn_operator.ex ↔ sidecar_configmap.ex spawn_operator/spawn_operator/lib/spawn_operator.ex:1— `spawn_operator/spawn_operator/lib/spawn_operator.ex` and `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/configmap/sidecar_configmap.ex` change together 81% of the time (51 of the 63 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 51 shared commits counted here, the most recent 3 are `057c1619` feat: add plugins behaviour and initial monitor plugin structure; `6c151f79` feat: share protobuf files between containers; `96436ff4` Relase minor version — run `git show` on any of them.
Change coupling: initializer.ex ↔ mix.exs spawn_initializer/lib/spawn_initializer/tls/initializer.ex:1— `spawn_initializer/lib/spawn_initializer/tls/initializer.ex` and `spawn_initializer/mix.exs` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Change coupling: actor_host_handler.ex ↔ sidecar_configmap.ex spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_host_handler.ex:1— `spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_host_handler.ex` and `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/configmap/sidecar_configmap.ex` change together 68% of the time (42 of the 62 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 42 shared commits counted here, the most recent 3 are `96436ff4` Relase minor version; `f4d629e4` New release version to fix alpine CVE; `b9bf185c` New minor release — run `git show` on any of them.
Change coupling: crdt_controller.ex ↔ manager_supervisor.ex lib/spawn/cluster/state_handoff/controllers/crdt_controller.ex:1— `lib/spawn/cluster/state_handoff/controllers/crdt_controller.ex` and `lib/spawn/cluster/state_handoff/manager_supervisor.ex` change together 56% of the time (10 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `e8c0c583` benchmark fix, invoke api compatibility and remove sbroker; `587d6db1` Refactor. Extract variables to system environments; `c265b650` Refactor. Rename — run `git show` on any of them.
Change coupling: flow.ex ↔ spawn_system.ex spawn_sdk/spawn_sdk/lib/flow.ex:1— `spawn_sdk/spawn_sdk/lib/flow.ex` and `spawn_sdk/spawn_sdk/lib/system/spawn_system.ex` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `78322768` fail backoff and flow meta; `54afd571` register ref on side effect; `ecc35ebc` Pubsub mechanism on register instead of relying on actor entity process — run `git show` on any of them.
Change coupling: actor.ex ↔ value.ex spawn_sdk/spawn_sdk/lib/actor.ex:1— `spawn_sdk/spawn_sdk/lib/actor.ex` and `spawn_sdk/spawn_sdk/lib/value.ex` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `2c2fceb9` add new interface to elixir sdk the same as typescript sdk; `3c015d07` Add actor support for tags and metadata; `93a3c1f2` oneof payload and forward — run `git show` on any of them.
Duplicated block (16 lines × 2) lib/_generated/spawn/actors/actor.pb.ex:1001— lib/_generated/spawn/actors/actor.pb.ex:1001-1016 | lib/_generated/spawn/actors/protocol.pb.ex:1523-1538 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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) spawn_operator/spawn_operator/lib/spawn_operator/k8s/activators/api.ex:43— spawn_operator/spawn_operator/lib/spawn_operator/k8s/activators/api.ex:43-58 | spawn_operator/spawn_operator/lib/spawn_operator/k8s/activators/rabbitmq.ex:19-34 — 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) spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:118— spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:118-133 | spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex:102-117 — before extracting anything, compare `spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex` and `spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 (16 lines × 2) lib/_generated/io/cloudevents/v1/spec.pb.ex:270— lib/_generated/io/cloudevents/v1/spec.pb.ex:270-285 | lib/_generated/spawn/actors/test.pb.ex:393-408 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/test.pb.ex` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 262 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 (16 lines × 2) spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:279— spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:279-294 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:383-398 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 365 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) lib/_generated/spawn/actors/healthcheck.pb.ex:495— lib/_generated/spawn/actors/healthcheck.pb.ex:495-503 | lib/_generated/spawn/actors/healthcheck.pb.ex:543-551 — 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) spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_system_handler.ex:50— spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_system_handler.ex:50-58 | spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_system_handler.ex:92-100 — 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) spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:309— spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:309-317 | spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex:223-231 — before extracting anything, compare `spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex` and `spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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) spawnctl/lib/spawnctl/commands/new/java.ex:229— spawnctl/lib/spawnctl/commands/new/java.ex:229-237 | spawnctl/lib/spawnctl/commands/new/node.ex:198-206 — before extracting anything, compare `spawnctl/lib/spawnctl/commands/new/java.ex` and `spawnctl/lib/spawnctl/commands/new/node.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 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) spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:362— spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:362-370 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:410-418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) lib/actors/security/tls/initializer.ex:26— lib/actors/security/tls/initializer.ex:26-44 | spawn_initializer/lib/spawn_initializer/tls/initializer.ex:27-45 — 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 (19 lines × 2) lib/sidecar/grpc/dispatcher.ex:195— lib/sidecar/grpc/dispatcher.ex:195-213 | lib/sidecar/grpc/dispatcher.ex:232-250 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) lib/sidecar/grpc/generators/actor_invoker_generator.ex:147— lib/sidecar/grpc/generators/actor_invoker_generator.ex:147-165 | lib/sidecar/grpc/generators/handler_generator.ex:68-86 — 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 × 2) spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex:68— spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex:68-86 | spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex:106-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 (18 lines × 2) lib/_generated/spawn/actors/actor.pb.ex:143— lib/_generated/spawn/actors/actor.pb.ex:143-160 | lib/_generated/spawn/actors/actor.pb.ex:764-781 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) lib/_generated/spawn/actors/healthcheck.pb.ex:216— lib/_generated/spawn/actors/healthcheck.pb.ex:216-233 | lib/_generated/spawn/actors/healthcheck.pb.ex:241-258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:6— spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:6-23 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:6-23 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 365 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) spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:38— spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:38-55 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:58-75 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 365 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.
Change-coupling hub: config.exs → customizer.ex, spawn_operator.ex, actor_host_handler.ex, sidecar_configmap.ex spawn_operator/spawn_operator/config/config.exs— `spawn_operator/spawn_operator/config/config.exs` changes together with 4 other files — `spawn_operator/spawn_operator/lib/mix/tasks/bonny.gen.manifest/customizer.ex`, `spawn_operator/spawn_operator/lib/spawn_operator.ex`, `spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_host_handler.ex`, `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/configmap/sidecar_configmap.ex` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: customizer.ex → spawn_operator.ex, actor_host_handler.ex, sidecar_configmap.ex spawn_operator/spawn_operator/lib/mix/tasks/bonny.gen.manifest/customizer.ex— `spawn_operator/spawn_operator/lib/mix/tasks/bonny.gen.manifest/customizer.ex` changes together with 3 other files — `spawn_operator/spawn_operator/lib/spawn_operator.ex`, `spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_host_handler.ex`, `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/configmap/sidecar_configmap.ex` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: deployment.ex → config.exs, customizer.ex, actor_host_handler.ex, sidecar_configmap.ex, hpa.ex, service.ex spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex— `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex` changes together with 6 other files — `spawn_operator/spawn_operator/config/config.exs`, `spawn_operator/spawn_operator/lib/mix/tasks/bonny.gen.manifest/customizer.ex`, `spawn_operator/spawn_operator/lib/spawn_operator/handler/actor_host_handler.ex`, `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/configmap/sidecar_configmap.ex`, `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/hpa.ex`, `spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/service.ex` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
Duplicated block (23 lines × 2) lib/_generated/spawn/actors/actor.pb.ex:379— lib/_generated/spawn/actors/actor.pb.ex:379-401 | lib/_generated/spawn/actors/state.pb.ex:7-29 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/state.pb.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 174 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 (23 lines × 2) lib/sidecar/grpc/dispatcher.ex:136— lib/sidecar/grpc/dispatcher.ex:136-158 | lib/sidecar/grpc/dispatcher.ex:164-186 — 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 (23 lines × 2) spawnctl/lib/spawnctl/commands/new/java.ex:177— spawnctl/lib/spawnctl/commands/new/java.ex:177-199 | spawnctl/lib/spawnctl/commands/new/java.ex:203-225 — 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 (21–22 lines × 2) lib/_generated/spawn/actors/actor.pb.ex:1097— lib/_generated/spawn/actors/actor.pb.ex:1097-1117 | lib/_generated/spawn/actors/protocol.pb.ex:1915-1936 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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 (21–22 lines × 2) spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_lookup_adapter.ex:42— spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_lookup_adapter.ex:42-63 | spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_lookup_adapter.ex:42-62 — 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 (21–22 lines × 2) spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:20— spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:20-40 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:42-63 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 7) lib/_generated/io/cloudevents/v1/spec.pb.ex:159— lib/_generated/io/cloudevents/v1/spec.pb.ex:159-178 | lib/_generated/io/cloudevents/v1/spec.pb.ex:461-480 | lib/_generated/spawn/actors/actor.pb.ex:289-308 | lib/_generated/spawn/actors/actor.pb.ex:336-355 | lib/_generated/spawn/actors/protocol.pb.ex:917-936 | lib/_generated/spawn/actors/protocol.pb.ex:1347-1366 | lib/_generated/spawn/actors/protocol.pb.ex:2026-2045 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (20 lines × 7) lib/_generated/spawn/actors/actor.pb.ex:1069— lib/_generated/spawn/actors/actor.pb.ex:1069-1088 | lib/_generated/spawn/actors/actor.pb.ex:1158-1177 | lib/_generated/spawn/actors/extensions.pb.ex:46-65 | lib/_generated/spawn/actors/extensions.pb.ex:88-107 | lib/_generated/spawn/actors/protocol.pb.ex:1529-1548 | lib/_generated/spawn/actors/protocol.pb.ex:1585-1604 | lib/_generated/spawn/actors/test.pb.ex:385-404 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/extensions.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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 (20 lines × 7) lib/_generated/spawn/actors/extensions.pb.ex:225— lib/_generated/spawn/actors/extensions.pb.ex:225-244 | lib/_generated/spawn/actors/protocol.pb.ex:642-661 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:353-372 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:10-29 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:49-68 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:94-113 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:122-141 — before extracting anything, compare `lib/_generated/spawn/actors/extensions.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 349 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) spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:263— spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:263-279 | spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:337-353 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/_generated/spawn/actors/test.pb.ex:316— lib/_generated/spawn/actors/test.pb.ex:316-332 | lib/_generated/spawn/actors/test.pb.ex:347-363 — 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) spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:62— spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:62-78 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:93-109 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 365 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 × 5) lib/_generated/spawn/actors/healthcheck.pb.ex:316— lib/_generated/spawn/actors/healthcheck.pb.ex:316-330 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:69-83 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:100-114 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:231-245 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:96-110 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (15 lines × 5) lib/_generated/spawn/actors/healthcheck.pb.ex:376— lib/_generated/spawn/actors/healthcheck.pb.ex:376-390 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:105-119 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:136-150 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:243-257 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:108-122 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (15 lines × 5) lib/_generated/io/cloudevents/v1/spec.pb.ex:101— lib/_generated/io/cloudevents/v1/spec.pb.ex:101-115 | lib/_generated/io/cloudevents/v1/spec.pb.ex:129-143 | lib/_generated/io/cloudevents/v1/spec.pb.ex:290-304 | lib/_generated/io/cloudevents/v1/spec.pb.ex:403-417 | lib/_generated/io/cloudevents/v1/spec.pb.ex:431-445 — 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 (11 lines × 2) spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:522— spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:522-532 | spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:556-566 — 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) REDACTED:133— REDACTED:133-143 | REDACTED:151-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:140— spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:140-150 | spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex:124-134 — before extracting anything, compare `spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex` and `spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 × 3) lib/actors/actor/caller_consumer.ex:270— lib/actors/actor/caller_consumer.ex:270-278 | lib/actors/actor/caller_consumer.ex:341-349 | lib/actors/actor/caller_consumer.ex:412-420 — 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 (9 lines × 3) lib/sidecar/grpc/generators/grpc_with_custom_options.ex:65— lib/sidecar/grpc/generators/grpc_with_custom_options.ex:65-73 | lib/sidecar/grpc/generators/handler_generator.ex:63-71 | lib/sidecar/grpc/generators/handler_transcoding_generator.ex:64-72 — before extracting anything, compare `lib/sidecar/grpc/generators/handler_generator.ex` and `lib/sidecar/grpc/generators/handler_transcoding_generator.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. 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 × 3) REDACTED:121— REDACTED:121-129 | REDACTED:129-137 | REDACTED:147-155 — 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 (7 lines × 2) spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:339— spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:339-345 | spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex:254-260 — before extracting anything, compare `spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex` and `spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 × 2) spawn_operator/spawn_operator/lib/spawn_operator/k8s_conn.ex:19— spawn_operator/spawn_operator/lib/spawn_operator/k8s_conn.ex:19-25 | spawnctl/lib/spawnctl/k8s/k8s_conn.ex:14-20 — 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 (7 lines × 2) spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:49— spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:49-55 | spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex:38-44 — before extracting anything, compare `spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex` and `spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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) spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:154— spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:154-158 | spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex:138-142 — before extracting anything, compare `spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex` and `spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 (5 lines × 2) lib/actors/config/name.ex:27— lib/actors/config/name.ex:27-31 | spawnctl/lib/spawnctl/util.ex:29-33 — 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 (5 lines × 2) spawn_operator/spawn_operator/lib/spawn_operator/controller/activator_controller.ex:16— spawn_operator/spawn_operator/lib/spawn_operator/controller/activator_controller.ex:16-20 | spawn_operator/spawn_operator/lib/spawn_operator/controller/actor_host_controller.ex:16-20 — 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.
Outbound HTTP without resilience spawnctl/lib/spawnctl/readme_fetcher.ex:12— `Req.get(` 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 spawnctl/lib/spawnctl/runtimes/behaviors/k8s_runtime.ex:47— `Req.get(` 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 spawnctl/lib/spawnctl/runtimes/behaviors/unix_runtime.ex:53— `Req.get(` 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.
Unbounded dependency requirement: bakeware — Runtime dependency `:bakeware` is declared `">= 0.0.0"` in spawn_initializer/mix.exs, which has no upper bound — every future MAJOR release of `:bakeware` 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.
Unbounded dependency requirement: bakeware — Runtime dependency `:bakeware` is declared `">= 0.0.0"` in spawn_operator/spawn_operator/mix.exs, which has no upper bound — every future MAJOR release of `:bakeware` 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.
Duplicated block (25 lines × 2) lib/_generated/spawn/actors/healthcheck.pb.ex:197— lib/_generated/spawn/actors/healthcheck.pb.ex:197-221 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:134-158 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 327 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 (25 lines × 2) spawnctl/lib/spawnctl/commands/new/java.ex:146— spawnctl/lib/spawnctl/commands/new/java.ex:146-170 | spawnctl/lib/spawnctl/commands/new/node.ex:135-159 — before extracting anything, compare `spawnctl/lib/spawnctl/commands/new/java.ex` and `spawnctl/lib/spawnctl/commands/new/node.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 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 (20–21 lines × 9) lib/_generated/io/cloudevents/v1/spec.pb.ex:256— lib/_generated/io/cloudevents/v1/spec.pb.ex:256-275 | lib/_generated/spawn/actors/actor.pb.ex:756-776 | lib/_generated/spawn/actors/actor.pb.ex:1421-1440 | lib/_generated/spawn/actors/extensions.pb.ex:124-143 | lib/_generated/spawn/actors/protocol.pb.ex:192-211 | lib/_generated/spawn/actors/protocol.pb.ex:1188-1207 | lib/_generated/spawn/actors/protocol.pb.ex:1311-1330 | lib/_generated/spawn/actors/protocol.pb.ex:1551-1570 | lib/_generated/spawn/actors/test.pb.ex:463-482 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (20–21 lines × 9) lib/_generated/spawn/actors/healthcheck.pb.ex:609— lib/_generated/spawn/actors/healthcheck.pb.ex:609-628 | lib/_generated/spawn/actors/healthcheck.pb.ex:657-677 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:178-198 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:209-228 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:257-277 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:460-479 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:508-528 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:229-248 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:277-297 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (21 lines × 2) lib/spawn/utils/common.ex:32— lib/spawn/utils/common.ex:32-52 | spawn_statestores/statestores/lib/statestores/util.ex:37-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 (21 lines × 2) spawnctl/lib/spawnctl/commands/new/java.ex:120— spawnctl/lib/spawnctl/commands/new/java.ex:120-140 | spawnctl/lib/spawnctl/commands/new/node.ex:109-129 — before extracting anything, compare `spawnctl/lib/spawnctl/commands/new/java.ex` and `spawnctl/lib/spawnctl/commands/new/node.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 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 (20 lines × 2) lib/sidecar/grpc/generators/handler_generator.ex:58— lib/sidecar/grpc/generators/handler_generator.ex:58-77 | lib/sidecar/grpc/generators/handler_transcoding_generator.ex:59-78 — before extracting anything, compare `lib/sidecar/grpc/generators/handler_generator.ex` and `lib/sidecar/grpc/generators/handler_transcoding_generator.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. 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 (20 lines × 2) spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:240— spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:240-259 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:105-124 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 386 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 (18 lines × 3) lib/_generated/spawn/actors/healthcheck.pb.ex:374— lib/_generated/spawn/actors/healthcheck.pb.ex:374-391 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:103-120 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:134-151 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (18 lines × 3) spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:333— spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:333-350 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:437-454 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:493-510 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 365 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 × 5) lib/_generated/spawn/actors/healthcheck.pb.ex:385— lib/_generated/spawn/actors/healthcheck.pb.ex:385-401 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:114-130 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:145-161 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:412-428 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:181-197 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (17 lines × 5) lib/_generated/spawn/actors/test.pb.ex:310— lib/_generated/spawn/actors/test.pb.ex:310-326 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:57-73 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:139-155 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:219-235 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:276-292 — before extracting anything, compare `lib/_generated/spawn/actors/test.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 221 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 × 9) lib/_generated/spawn/actors/healthcheck.pb.ex:321— lib/_generated/spawn/actors/healthcheck.pb.ex:321-334 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:74-87 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:105-118 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:236-249 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:252-265 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:284-297 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:101-114 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:117-130 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:149-162 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 × 9) lib/_generated/spawn/actors/healthcheck.pb.ex:569— lib/_generated/spawn/actors/healthcheck.pb.ex:569-582 | lib/_generated/spawn/actors/healthcheck.pb.ex:625-638 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:138-151 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:169-182 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:225-238 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:428-441 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:476-489 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:197-210 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:245-258 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 × 8) lib/_generated/spawn/actors/actor.pb.ex:754— lib/_generated/spawn/actors/actor.pb.ex:754-767 | lib/_generated/spawn/actors/actor.pb.ex:1419-1432 | lib/_generated/spawn/actors/extensions.pb.ex:122-135 | lib/_generated/spawn/actors/protocol.pb.ex:190-203 | lib/_generated/spawn/actors/protocol.pb.ex:1186-1199 | lib/_generated/spawn/actors/protocol.pb.ex:1309-1322 | lib/_generated/spawn/actors/protocol.pb.ex:1549-1562 | lib/_generated/spawn/actors/test.pb.ex:447-460 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/extensions.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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 × 8) lib/_generated/spawn/actors/healthcheck.pb.ex:345— lib/_generated/spawn/actors/healthcheck.pb.ex:345-358 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:82-95 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:113-126 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:276-289 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:300-313 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:364-377 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:141-154 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:165-178 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 × 5) lib/_generated/io/cloudevents/v1/spec.pb.ex:368— lib/_generated/io/cloudevents/v1/spec.pb.ex:368-380 | lib/_generated/spawn/actors/healthcheck.pb.ex:177-189 | lib/_generated/spawn/actors/protocol.pb.ex:304-316 | lib/_generated/spawn/actors/test.pb.ex:622-634 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:114-126 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/healthcheck.pb.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 151 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 × 5) lib/_generated/spawn/actors/test.pb.ex:332— lib/_generated/spawn/actors/test.pb.ex:332-344 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:74-86 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:156-168 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:236-248 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:293-305 — before extracting anything, compare `lib/_generated/spawn/actors/test.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 221 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) lib/sidecar/grpc/generators/actor_invoker_generator.ex:123— lib/sidecar/grpc/generators/actor_invoker_generator.ex:123-129 | lib/sidecar/grpc/generators/handler_generator.ex:44-50 | lib/sidecar/grpc/generators/handler_transcoding_generator.ex:45-51 — before extracting anything, compare `lib/sidecar/grpc/generators/handler_generator.ex` and `lib/sidecar/grpc/generators/handler_transcoding_generator.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. 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) spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:159— spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:159-165 | spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex:140-146 | spawnctl/lib/spawnctl/commands/playground/k8s/minikube.ex:179-185 — before extracting anything, compare `spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex` and `spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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.
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.
CallerConsumer.invoke_with_span (cognitive 19) lib/actors/actor/caller_consumer.ex:529— CallerConsumer.invoke_with_span has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 3 (5 pts), error handling 2, boolean chains 1 (nesting depth added 4). 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.
StateManager.save_async (cognitive 16) lib/actors/actor/state_manager.ex:155— StateManager.save_async has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 2 (6 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Near-duplicate member family (17 members, 50 shared lines) · ×1
Near-duplicate member family (17 members, 50 shared lines) lib/_generated/io/cloudevents/v1/spec.pb.ex:7— lib/_generated/io/cloudevents/v1/spec.pb.ex:7-58 | lib/_generated/io/cloudevents/v1/spec.pb.ex:204-502 | lib/_generated/spawn/actors/actor.pb.ex:75-126 | lib/_generated/spawn/actors/actor.pb.ex:139-219 | lib/_generated/spawn/actors/actor.pb.ex:511-562 | lib/_generated/spawn/actors/actor.pb.ex:575-669 | lib/_generated/spawn/actors/actor.pb.ex:682-733 | lib/_generated/spawn/actors/actor.pb.ex:746-840 | lib/_generated/spawn/actors/protocol.pb.ex:54-105 | lib/_generated/spawn/actors/protocol.pb.ex:118-169 | lib/_generated/spawn/actors/protocol.pb.ex:182-370 | lib/_generated/spawn/actors/protocol.pb.ex:1100-1151 | lib/_generated/spawn/actors/protocol.pb.ex:1164-1286 | lib/_generated/spawn/actors/protocol.pb.ex:1393-1444 | lib/_generated/spawn/actors/protocol.pb.ex:1457-1683 | lib/_generated/spawn/actors/test.pb.ex:243-294 | lib/_generated/spawn/actors/test.pb.ex:307-688 — These 17 members are variants of one another: a block of 50 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 17 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 17 times.
D4 · Code Duplication· Near-duplicate member family (9 members, 42 shared lines) · ×1
Near-duplicate member family (9 members, 42 shared lines) lib/_generated/io/cloudevents/v1/spec.pb.ex:204— lib/_generated/io/cloudevents/v1/spec.pb.ex:204-502 | lib/_generated/spawn/actors/actor.pb.ex:575-669 | lib/_generated/spawn/actors/extensions.pb.ex:30-169 | lib/_generated/spawn/actors/protocol.pb.ex:182-370 | lib/_generated/spawn/actors/protocol.pb.ex:1164-1286 | lib/_generated/spawn/actors/protocol.pb.ex:1457-1683 | lib/_generated/spawn/actors/protocol.pb.ex:1707-1810 | lib/_generated/spawn/actors/protocol.pb.ex:1829-1946 | lib/_generated/spawn/actors/test.pb.ex:307-688 — These 9 members are variants of one another: a block of 42 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 9 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 9 times.
D4 · Code Duplication· Near-duplicate member family (8 members, 40 shared lines) · ×1
Near-duplicate member family (8 members, 40 shared lines) lib/_generated/io/cloudevents/v1/spec.pb.ex:204— lib/_generated/io/cloudevents/v1/spec.pb.ex:204-502 | lib/_generated/spawn/actors/actor.pb.ex:575-669 | lib/_generated/spawn/actors/actor.pb.ex:746-840 | lib/_generated/spawn/actors/extensions.pb.ex:30-169 | lib/_generated/spawn/actors/protocol.pb.ex:182-370 | lib/_generated/spawn/actors/protocol.pb.ex:1164-1286 | lib/_generated/spawn/actors/protocol.pb.ex:1457-1683 | lib/_generated/spawn/actors/test.pb.ex:307-688 — These 8 members are variants of one another: a block of 40 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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· Near-duplicate member family (7 members, 61 shared lines) · ×1
Near-duplicate member family (7 members, 61 shared lines) lib/_generated/spawn/actors/actor.pb.ex:1142— lib/_generated/spawn/actors/actor.pb.ex:1142-1267 | lib/_generated/spawn/actors/protocol.pb.ex:182-370 | lib/_generated/spawn/actors/protocol.pb.ex:1164-1286 | lib/_generated/spawn/actors/protocol.pb.ex:1457-1683 | lib/_generated/spawn/actors/protocol.pb.ex:1707-1810 | lib/_generated/spawn/actors/protocol.pb.ex:1829-1946 | lib/_generated/spawn/actors/test.pb.ex:307-688 — These 7 members are variants of one another: a block of 61 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 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 7 times.
D4 · Code Duplication· Near-duplicate member family (7 members, 57 shared lines) · ×1
Near-duplicate member family (7 members, 57 shared lines) lib/_generated/spawn/actors/actor.pb.ex:575— lib/_generated/spawn/actors/actor.pb.ex:575-669 | lib/_generated/spawn/actors/actor.pb.ex:746-840 | lib/_generated/spawn/actors/protocol.pb.ex:182-370 | lib/_generated/spawn/actors/protocol.pb.ex:1164-1286 | lib/_generated/spawn/actors/test.pb.ex:101-227 | lib/_generated/spawn/actors/test.pb.ex:307-688 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:202-336 — These 7 members are variants of one another: a block of 57 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 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 7 times.
D4 · Code Duplication· Near-duplicate member family (7 members, 47 shared lines) · ×1
Near-duplicate member family (7 members, 47 shared lines) lib/_generated/spawn/actors/actor.pb.ex:575— lib/_generated/spawn/actors/actor.pb.ex:575-669 | lib/_generated/spawn/actors/actor.pb.ex:1142-1267 | lib/_generated/spawn/actors/protocol.pb.ex:182-370 | lib/_generated/spawn/actors/protocol.pb.ex:1164-1286 | lib/_generated/spawn/actors/protocol.pb.ex:1457-1683 | lib/_generated/spawn/actors/test.pb.ex:101-227 | lib/_generated/spawn/actors/test.pb.ex:307-688 — These 7 members are variants of one another: a block of 47 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 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 7 times.
D4 · Code Duplication· Near-duplicate member family (7 members, 46 shared lines) · ×1
Near-duplicate member family (7 members, 46 shared lines) lib/_generated/io/cloudevents/v1/spec.pb.ex:204— lib/_generated/io/cloudevents/v1/spec.pb.ex:204-502 | lib/_generated/spawn/actors/protocol.pb.ex:885-946 | lib/_generated/spawn/actors/protocol.pb.ex:1301-1376 | lib/_generated/spawn/actors/protocol.pb.ex:1457-1683 | lib/_generated/spawn/actors/protocol.pb.ex:1707-1810 | lib/_generated/spawn/actors/protocol.pb.ex:1829-1946 | lib/_generated/spawn/actors/protocol.pb.ex:1966-2055 — These 7 members are variants of one another: a block of 46 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 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 7 times.
D4 · Code Duplication· Near-duplicate member family (7 members, 43 shared lines) · ×1
Near-duplicate member family (7 members, 43 shared lines) lib/_generated/spawn/actors/actor.pb.ex:139— lib/_generated/spawn/actors/actor.pb.ex:139-219 | lib/_generated/spawn/actors/actor.pb.ex:575-669 | lib/_generated/spawn/actors/actor.pb.ex:746-840 | lib/_generated/spawn/actors/protocol.pb.ex:182-370 | lib/_generated/spawn/actors/protocol.pb.ex:1164-1286 | lib/_generated/spawn/actors/test.pb.ex:101-227 | lib/_generated/spawn/actors/test.pb.ex:307-688 — These 7 members are variants of one another: a block of 43 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 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 7 times.
D4 · Code Duplication· Near-duplicate member family (6 members, 37 shared lines) · ×1
Near-duplicate member family (6 members, 37 shared lines) lib/_generated/spawn/actors/actor.pb.ex:457— lib/_generated/spawn/actors/actor.pb.ex:457-498 | lib/_generated/spawn/actors/actor.pb.ex:1142-1267 | lib/_generated/spawn/actors/protocol.pb.ex:555-666 | lib/_generated/spawn/actors/protocol.pb.ex:762-831 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:40-121 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:202-336 — These 6 members are variants of one another: a block of 37 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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.
D4 · Code Duplication· Near-duplicate member family (5 members, 125 shared lines) · ×1
Near-duplicate member family (5 members, 125 shared lines) lib/_generated/spawn/actors/healthcheck.pb.ex:116— lib/_generated/spawn/actors/healthcheck.pb.ex:116-687 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:6-207 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:6-286 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:86-537 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:8-306 — These 5 members are variants of one another: a block of 125 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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.
D4 · Code Duplication· Near-duplicate member family (4 members, 58 shared lines) · ×1
Near-duplicate member family (4 members, 58 shared lines) lib/_generated/spawn/actors/actor.pb.ex:1053— lib/_generated/spawn/actors/actor.pb.ex:1053-1122 | lib/_generated/spawn/actors/actor.pb.ex:1369-1466 | lib/_generated/spawn/actors/extensions.pb.ex:30-169 | lib/_generated/spawn/actors/test.pb.ex:307-688 — These 4 members are variants of one another: a block of 58 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) spawn_operator/spawn_operator/lib/spawn_operator/k8s/plugins/monitor/monitor_plugin.ex:96— spawn_operator/spawn_operator/lib/spawn_operator/k8s/plugins/monitor/monitor_plugin.ex:96-168 | spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:101-204 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:67— spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:67-115 | spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:122-152 | spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex:56-96 | spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex:103-133 | spawnctl/lib/spawnctl/commands/playground/k8s/minikube.ex:58-98 — 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/_generated/spawn/actors/actor.pb.ex:7— lib/_generated/spawn/actors/actor.pb.ex:7-57 | lib/_generated/spawn/actors/protocol.pb.ex:7-39 | lib/_generated/spawn/actors/test.pb.ex:7-33 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:7-27 — 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 (44 lines × 2) spawn_operator/spawn_operator/lib/spawn_operator/k8s/plugins/monitor/monitor_plugin.ex:172— spawn_operator/spawn_operator/lib/spawn_operator/k8s/plugins/monitor/monitor_plugin.ex:172-215 | spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:208-251 — 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 (24–36 lines × 2) spawn_operator/spawn_operator/lib/spawn_operator/versions/api/v1/actor_host.ex:281— spawn_operator/spawn_operator/lib/spawn_operator/versions/api/v1/actor_host.ex:281-316 | spawn_operator/spawn_operator/lib/spawn_operator/versions/api/v1/actor_system.ex:85-108 — 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 (35–36 lines × 2) spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:381— spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:381-416 | spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex:343-377 — before extracting anything, compare `spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex` and `spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 (33–36 lines × 2) spawnctl/lib/spawnctl/commands/playground/new.ex:187— spawnctl/lib/spawnctl/commands/playground/new.ex:187-219 | spawnctl/lib/spawnctl/runtimes/behaviors/k8s_runtime.ex:59-94 — 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 (34 lines × 2) lib/actors/actor/entity/invocation.ex:713— lib/actors/actor/entity/invocation.ex:713-746 | lib/actors/actor/entity/invocation.ex:764-797 — 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 (33–34 lines × 2) spawn_operator/spawn_operator/lib/spawn_operator/k8s/plugins/monitor/monitor_plugin.ex:99— spawn_operator/spawn_operator/lib/spawn_operator/k8s/plugins/monitor/monitor_plugin.ex:99-131 | spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:148-181 — 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 (32–33 lines × 2) spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:213— spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:213-245 | spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex:183-214 — before extracting anything, compare `spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex` and `spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 (31 lines × 2) spawnctl/lib/spawnctl/commands/playground/k8s/minikube.ex:105— spawnctl/lib/spawnctl/commands/playground/k8s/minikube.ex:105-135 | spawnctl/lib/spawnctl/commands/playground/k8s/minikube.ex:142-172 — 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 (28–29 lines × 3) spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:87— spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:87-115 | spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex:69-96 | spawnctl/lib/spawnctl/commands/playground/k8s/minikube.ex:71-98 — before extracting anything, compare `spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex` and `spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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 (27–28 lines × 18) lib/_generated/io/cloudevents/v1/spec.pb.ex:31— lib/_generated/io/cloudevents/v1/spec.pb.ex:31-58 | lib/_generated/io/cloudevents/v1/spec.pb.ex:345-371 | lib/_generated/spawn/actors/actor.pb.ex:99-126 | lib/_generated/spawn/actors/actor.pb.ex:182-209 | lib/_generated/spawn/actors/actor.pb.ex:535-562 | lib/_generated/spawn/actors/actor.pb.ex:632-659 | lib/_generated/spawn/actors/actor.pb.ex:706-733 | lib/_generated/spawn/actors/actor.pb.ex:803-830 | lib/_generated/spawn/actors/protocol.pb.ex:78-105 | lib/_generated/spawn/actors/protocol.pb.ex:142-169 | lib/_generated/spawn/actors/protocol.pb.ex:281-307 | lib/_generated/spawn/actors/protocol.pb.ex:333-360 | lib/_generated/spawn/actors/protocol.pb.ex:1124-1151 | lib/_generated/spawn/actors/protocol.pb.ex:1249-1276 | lib/_generated/spawn/actors/protocol.pb.ex:1417-1444 | lib/_generated/spawn/actors/protocol.pb.ex:1640-1667 | lib/_generated/spawn/actors/test.pb.ex:267-294 | lib/_generated/spawn/actors/test.pb.ex:651-678 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (21–28 lines × 9) lib/_generated/io/cloudevents/v1/spec.pb.ex:151— lib/_generated/io/cloudevents/v1/spec.pb.ex:151-171 | lib/_generated/io/cloudevents/v1/spec.pb.ex:298-318 | lib/_generated/io/cloudevents/v1/spec.pb.ex:453-473 | lib/_generated/spawn/actors/protocol.pb.ex:898-925 | lib/_generated/spawn/actors/protocol.pb.ex:1328-1355 | lib/_generated/spawn/actors/protocol.pb.ex:1498-1525 | lib/_generated/spawn/actors/protocol.pb.ex:1748-1775 | lib/_generated/spawn/actors/protocol.pb.ex:1870-1897 | lib/_generated/spawn/actors/protocol.pb.ex:2007-2034 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 381 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 (21–28 lines × 4) lib/_generated/spawn/actors/actor.pb.ex:1194— lib/_generated/spawn/actors/actor.pb.ex:1194-1221 | lib/_generated/spawn/actors/extensions.pb.ex:217-238 | lib/_generated/spawn/actors/protocol.pb.ex:620-640 | lib/_generated/spawn/actors/protocol.pb.ex:771-791 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/extensions.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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 (28 lines × 2) lib/spawn/cluster/state_handoff/controllers/crdt_controller.ex:189— lib/spawn/cluster/state_handoff/controllers/crdt_controller.ex:189-216 | lib/spawn/cluster/state_handoff/invocation_scheduler_state.ex:131-158 — 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 (27 lines × 2) spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:126— spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex:126-152 | spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex:107-133 — before extracting anything, compare `spawnctl/lib/spawnctl/commands/playground/k8s/k3d.ex` and `spawnctl/lib/spawnctl/commands/playground/k8s/kind.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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 (26 lines × 2) lib/_generated/spawn/actors/extensions.pb.ex:54— lib/_generated/spawn/actors/extensions.pb.ex:54-79 | lib/_generated/spawn/actors/protocol.pb.ex:1565-1590 — before extracting anything, compare `lib/_generated/spawn/actors/extensions.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 349 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 (23–26 lines × 2) spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:58— spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:58-83 | spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex:61-83 — before extracting anything, compare `spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex` and `spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 (24–25 lines × 2) lib/_generated/spawn/actors/extensions.pb.ex:136— lib/_generated/spawn/actors/extensions.pb.ex:136-159 | lib/_generated/spawn/actors/test.pb.ex:475-499 — before extracting anything, compare `lib/_generated/spawn/actors/extensions.pb.ex` and `lib/_generated/spawn/actors/test.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 319 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 (19–20 lines × 3) lib/_generated/spawn/actors/actor.pb.ex:8— lib/_generated/spawn/actors/actor.pb.ex:8-26 | lib/_generated/spawn/actors/protocol.pb.ex:8-26 | lib/_generated/spawn/actors/test.pb.ex:8-27 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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 (19 lines × 41) lib/_generated/io/cloudevents/v1/spec.pb.ex:10— lib/_generated/io/cloudevents/v1/spec.pb.ex:10-28 | lib/_generated/io/cloudevents/v1/spec.pb.ex:207-225 | lib/_generated/io/cloudevents/v1/spec.pb.ex:324-342 | lib/_generated/spawn/actors/actor.pb.ex:78-96 | lib/_generated/spawn/actors/actor.pb.ex:161-179 | lib/_generated/spawn/actors/actor.pb.ex:234-252 | lib/_generated/spawn/actors/actor.pb.ex:514-532 | lib/_generated/spawn/actors/actor.pb.ex:611-629 | lib/_generated/spawn/actors/actor.pb.ex:685-703 | lib/_generated/spawn/actors/actor.pb.ex:782-800 | lib/_generated/spawn/actors/actor.pb.ex:856-874 | lib/_generated/spawn/actors/actor.pb.ex:910-928 | lib/_generated/spawn/actors/actor.pb.ex:1303-1321 | lib/_generated/spawn/actors/extensions.pb.ex:33-51 | lib/_generated/spawn/actors/extensions.pb.ex:197-215 | lib/_generated/spawn/actors/healthcheck.pb.ex:10-28 | lib/_generated/spawn/actors/healthcheck.pb.ex:129-147 | lib/_generated/spawn/actors/protocol.pb.ex:57-75 | lib/_generated/spawn/actors/protocol.pb.ex:121-139 | lib/_generated/spawn/actors/protocol.pb.ex:260-278 | lib/_generated/spawn/actors/protocol.pb.ex:312-330 | lib/_generated/spawn/actors/protocol.pb.ex:558-576 | lib/_generated/spawn/actors/protocol.pb.ex:793-811 | lib/_generated/spawn/actors/protocol.pb.ex:888-906 | lib/_generated/spawn/actors/protocol.pb.ex:965-983 | lib/_generated/spawn/actors/protocol.pb.ex:1034-1052 | lib/_generated/spawn/actors/protocol.pb.ex:1103-1121 | lib/_generated/spawn/actors/protocol.pb.ex:1167-1185 | lib/_generated/spawn/actors/protocol.pb.ex:1228-1246 | lib/_generated/spawn/actors/protocol.pb.ex:1396-1414 | lib/_generated/spawn/actors/protocol.pb.ex:1488-1506 | lib/_generated/spawn/actors/protocol.pb.ex:1619-1637 | lib/_generated/spawn/actors/protocol.pb.ex:1724-1742 | lib/_generated/spawn/actors/protocol.pb.ex:1832-1850 | lib/_generated/spawn/actors/test.pb.ex:50-68 | lib/_generated/spawn/actors/test.pb.ex:104-122 | lib/_generated/spawn/actors/test.pb.ex:179-197 | lib/_generated/spawn/actors/test.pb.ex:246-264 | lib/_generated/spawn/actors/test.pb.ex:503-521 | lib/_generated/spawn/actors/test.pb.ex:578-596 | lib/_generated/spawn/actors/test.pb.ex:630-648 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (18–19 lines × 39) lib/_generated/io/cloudevents/v1/spec.pb.ex:216— lib/_generated/io/cloudevents/v1/spec.pb.ex:216-233 | lib/_generated/spawn/actors/actor.pb.ex:523-541 | lib/_generated/spawn/actors/actor.pb.ex:620-638 | lib/_generated/spawn/actors/actor.pb.ex:694-712 | lib/_generated/spawn/actors/actor.pb.ex:791-809 | lib/_generated/spawn/actors/actor.pb.ex:865-883 | lib/_generated/spawn/actors/actor.pb.ex:919-936 | lib/_generated/spawn/actors/actor.pb.ex:1238-1256 | lib/_generated/spawn/actors/actor.pb.ex:1312-1329 | lib/_generated/spawn/actors/extensions.pb.ex:206-223 | lib/_generated/spawn/actors/healthcheck.pb.ex:19-36 | lib/_generated/spawn/actors/healthcheck.pb.ex:138-155 | lib/_generated/spawn/actors/protocol.pb.ex:66-84 | lib/_generated/spawn/actors/protocol.pb.ex:130-148 | lib/_generated/spawn/actors/protocol.pb.ex:269-287 | lib/_generated/spawn/actors/protocol.pb.ex:321-339 | lib/_generated/spawn/actors/protocol.pb.ex:567-584 | lib/_generated/spawn/actors/protocol.pb.ex:788-805 | lib/_generated/spawn/actors/protocol.pb.ex:974-991 | lib/_generated/spawn/actors/protocol.pb.ex:1043-1060 | lib/_generated/spawn/actors/protocol.pb.ex:1112-1130 | lib/_generated/spawn/actors/protocol.pb.ex:1237-1255 | lib/_generated/spawn/actors/protocol.pb.ex:1405-1423 | lib/_generated/spawn/actors/protocol.pb.ex:1483-1500 | lib/_generated/spawn/actors/protocol.pb.ex:1595-1613 | lib/_generated/spawn/actors/protocol.pb.ex:1628-1646 | lib/_generated/spawn/actors/protocol.pb.ex:1719-1736 | lib/_generated/spawn/actors/protocol.pb.ex:1841-1858 | lib/_generated/spawn/actors/protocol.pb.ex:2085-2103 | lib/_generated/spawn/actors/test.pb.ex:59-77 | lib/_generated/spawn/actors/test.pb.ex:113-130 | lib/_generated/spawn/actors/test.pb.ex:188-206 | lib/_generated/spawn/actors/test.pb.ex:255-273 | lib/_generated/spawn/actors/test.pb.ex:512-529 | lib/_generated/spawn/actors/test.pb.ex:587-605 | lib/_generated/spawn/actors/test.pb.ex:639-657 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:92-110 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:160-178 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:297-315 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (15–19 lines × 10) lib/_generated/io/cloudevents/v1/spec.pb.ex:168— lib/_generated/io/cloudevents/v1/spec.pb.ex:168-182 | lib/_generated/io/cloudevents/v1/spec.pb.ex:470-488 | lib/_generated/spawn/actors/actor.pb.ex:298-316 | lib/_generated/spawn/actors/actor.pb.ex:345-363 | lib/_generated/spawn/actors/actor.pb.ex:1018-1036 | lib/_generated/spawn/actors/protocol.pb.ex:926-944 | lib/_generated/spawn/actors/protocol.pb.ex:1356-1374 | lib/_generated/spawn/actors/protocol.pb.ex:1790-1808 | lib/_generated/spawn/actors/protocol.pb.ex:1926-1944 | lib/_generated/spawn/actors/protocol.pb.ex:2035-2053 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (19 lines × 6) lib/_generated/spawn/actors/actor.pb.ex:460— lib/_generated/spawn/actors/actor.pb.ex:460-478 | lib/_generated/spawn/actors/actor.pb.ex:1201-1219 | lib/_generated/spawn/actors/protocol.pb.ex:628-646 | lib/_generated/spawn/actors/protocol.pb.ex:765-783 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:43-61 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:205-223 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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 (19 lines × 3) lib/_generated/spawn/actors/actor.pb.ex:1145— lib/_generated/spawn/actors/actor.pb.ex:1145-1163 | lib/_generated/spawn/actors/protocol.pb.ex:2076-2094 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:83-101 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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) lib/_generated/spawn/actors/extensions.pb.ex:140— lib/_generated/spawn/actors/extensions.pb.ex:140-158 | lib/_generated/spawn/actors/test.pb.ex:479-497 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:78-95 — before extracting anything, compare `lib/_generated/spawn/actors/extensions.pb.ex` and `lib/_generated/spawn/actors/test.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 319 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–18 lines × 41) lib/_generated/spawn/actors/actor.pb.ex:255— lib/_generated/spawn/actors/actor.pb.ex:255-272 | lib/_generated/spawn/actors/actor.pb.ex:389-406 | lib/_generated/spawn/actors/actor.pb.ex:428-445 | lib/_generated/spawn/actors/actor.pb.ex:481-498 | lib/_generated/spawn/actors/actor.pb.ex:877-894 | lib/_generated/spawn/actors/actor.pb.ex:959-976 | lib/_generated/spawn/actors/actor.pb.ex:1105-1122 | lib/_generated/spawn/actors/actor.pb.ex:1250-1267 | lib/_generated/spawn/actors/actor.pb.ex:1338-1355 | lib/_generated/spawn/actors/actor.pb.ex:1449-1466 | lib/_generated/spawn/actors/extensions.pb.ex:152-169 | lib/_generated/spawn/actors/extensions.pb.ex:232-249 | lib/_generated/spawn/actors/healthcheck.pb.ex:45-62 | lib/_generated/spawn/actors/healthcheck.pb.ex:86-103 | lib/_generated/spawn/actors/healthcheck.pb.ex:164-180 | lib/_generated/spawn/actors/healthcheck.pb.ex:192-209 | lib/_generated/spawn/actors/protocol.pb.ex:418-435 | lib/_generated/spawn/actors/protocol.pb.ex:471-488 | lib/_generated/spawn/actors/protocol.pb.ex:525-542 | lib/_generated/spawn/actors/protocol.pb.ex:649-666 | lib/_generated/spawn/actors/protocol.pb.ex:694-711 | lib/_generated/spawn/actors/protocol.pb.ex:733-750 | lib/_generated/spawn/actors/protocol.pb.ex:814-831 | lib/_generated/spawn/actors/protocol.pb.ex:856-873 | lib/_generated/spawn/actors/protocol.pb.ex:1000-1017 | lib/_generated/spawn/actors/protocol.pb.ex:1069-1086 | lib/_generated/spawn/actors/protocol.pb.ex:2097-2114 | lib/_generated/spawn/actors/state.pb.ex:17-34 | lib/_generated/spawn/actors/state.pb.ex:70-87 | lib/_generated/spawn/actors/test.pb.ex:71-88 | lib/_generated/spawn/actors/test.pb.ex:200-217 | lib/_generated/spawn/actors/test.pb.ex:599-616 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:104-121 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:172-189 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:309-326 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:360-377 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:399-416 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:17-34 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:56-73 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:101-117 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:129-146 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/extensions.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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–18 lines × 31) lib/_generated/io/cloudevents/v1/spec.pb.ex:20— lib/_generated/io/cloudevents/v1/spec.pb.ex:20-37 | lib/_generated/io/cloudevents/v1/spec.pb.ex:334-351 | lib/_generated/spawn/actors/actor.pb.ex:88-105 | lib/_generated/spawn/actors/actor.pb.ex:171-188 | lib/_generated/spawn/actors/actor.pb.ex:244-261 | lib/_generated/spawn/actors/actor.pb.ex:470-487 | lib/_generated/spawn/actors/actor.pb.ex:588-605 | lib/_generated/spawn/actors/actor.pb.ex:948-965 | lib/_generated/spawn/actors/actor.pb.ex:1080-1096 | lib/_generated/spawn/actors/actor.pb.ex:1169-1185 | lib/_generated/spawn/actors/actor.pb.ex:1225-1241 | lib/_generated/spawn/actors/actor.pb.ex:1382-1398 | lib/_generated/spawn/actors/extensions.pb.ex:113-129 | lib/_generated/spawn/actors/healthcheck.pb.ex:34-51 | lib/_generated/spawn/actors/healthcheck.pb.ex:153-170 | lib/_generated/spawn/actors/protocol.pb.ex:223-239 | lib/_generated/spawn/actors/protocol.pb.ex:460-477 | lib/_generated/spawn/actors/protocol.pb.ex:514-531 | lib/_generated/spawn/actors/protocol.pb.ex:1177-1193 | lib/_generated/spawn/actors/protocol.pb.ex:1205-1222 | lib/_generated/spawn/actors/protocol.pb.ex:1470-1486 | lib/_generated/spawn/actors/protocol.pb.ex:1540-1556 | lib/_generated/spawn/actors/protocol.pb.ex:1734-1750 | lib/_generated/spawn/actors/protocol.pb.ex:1776-1793 | lib/_generated/spawn/actors/protocol.pb.ex:1856-1872 | lib/_generated/spawn/actors/protocol.pb.ex:1898-1914 | lib/_generated/spawn/actors/protocol.pb.ex:1979-1995 | lib/_generated/spawn/actors/state.pb.ex:59-76 | lib/_generated/spawn/actors/test.pb.ex:156-173 | lib/_generated/spawn/actors/test.pb.ex:410-426 | lib/_generated/spawn/actors/test.pb.ex:555-572 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (18 lines × 29) lib/_generated/spawn/actors/actor.pb.ex:422— lib/_generated/spawn/actors/actor.pb.ex:422-439 | lib/_generated/spawn/actors/actor.pb.ex:529-546 | lib/_generated/spawn/actors/actor.pb.ex:626-643 | lib/_generated/spawn/actors/actor.pb.ex:700-717 | lib/_generated/spawn/actors/actor.pb.ex:797-814 | lib/_generated/spawn/actors/actor.pb.ex:871-888 | lib/_generated/spawn/actors/actor.pb.ex:1244-1261 | lib/_generated/spawn/actors/actor.pb.ex:1332-1349 | lib/_generated/spawn/actors/protocol.pb.ex:72-89 | lib/_generated/spawn/actors/protocol.pb.ex:136-153 | lib/_generated/spawn/actors/protocol.pb.ex:275-292 | lib/_generated/spawn/actors/protocol.pb.ex:327-344 | lib/_generated/spawn/actors/protocol.pb.ex:412-429 | lib/_generated/spawn/actors/protocol.pb.ex:808-825 | lib/_generated/spawn/actors/protocol.pb.ex:994-1011 | lib/_generated/spawn/actors/protocol.pb.ex:1063-1080 | lib/_generated/spawn/actors/protocol.pb.ex:1118-1135 | lib/_generated/spawn/actors/protocol.pb.ex:1243-1260 | lib/_generated/spawn/actors/protocol.pb.ex:1411-1428 | lib/_generated/spawn/actors/protocol.pb.ex:1634-1651 | lib/_generated/spawn/actors/protocol.pb.ex:2091-2108 | lib/_generated/spawn/actors/test.pb.ex:65-82 | lib/_generated/spawn/actors/test.pb.ex:194-211 | lib/_generated/spawn/actors/test.pb.ex:261-278 | lib/_generated/spawn/actors/test.pb.ex:593-610 | lib/_generated/spawn/actors/test.pb.ex:645-662 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:98-115 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:166-183 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:303-320 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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 × 20) lib/_generated/spawn/actors/actor.pb.ex:1084— lib/_generated/spawn/actors/actor.pb.ex:1084-1101 | lib/_generated/spawn/actors/actor.pb.ex:1173-1190 | lib/_generated/spawn/actors/actor.pb.ex:1229-1246 | lib/_generated/spawn/actors/actor.pb.ex:1372-1389 | lib/_generated/spawn/actors/extensions.pb.ex:117-134 | lib/_generated/spawn/actors/protocol.pb.ex:185-202 | lib/_generated/spawn/actors/protocol.pb.ex:227-244 | lib/_generated/spawn/actors/protocol.pb.ex:450-467 | lib/_generated/spawn/actors/protocol.pb.ex:504-521 | lib/_generated/spawn/actors/protocol.pb.ex:1181-1198 | lib/_generated/spawn/actors/protocol.pb.ex:1304-1321 | lib/_generated/spawn/actors/protocol.pb.ex:1460-1477 | lib/_generated/spawn/actors/protocol.pb.ex:1544-1561 | lib/_generated/spawn/actors/protocol.pb.ex:1710-1727 | lib/_generated/spawn/actors/protocol.pb.ex:1738-1755 | lib/_generated/spawn/actors/protocol.pb.ex:1860-1877 | lib/_generated/spawn/actors/protocol.pb.ex:1902-1919 | lib/_generated/spawn/actors/protocol.pb.ex:1969-1986 | lib/_generated/spawn/actors/state.pb.ex:49-66 | lib/_generated/spawn/actors/test.pb.ex:414-431 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/extensions.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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 × 17) lib/_generated/io/cloudevents/v1/spec.pb.ex:25— lib/_generated/io/cloudevents/v1/spec.pb.ex:25-42 | lib/_generated/io/cloudevents/v1/spec.pb.ex:339-356 | lib/_generated/spawn/actors/actor.pb.ex:93-110 | lib/_generated/spawn/actors/actor.pb.ex:176-193 | lib/_generated/spawn/actors/actor.pb.ex:249-266 | lib/_generated/spawn/actors/actor.pb.ex:475-492 | lib/_generated/spawn/actors/actor.pb.ex:953-970 | lib/_generated/spawn/actors/healthcheck.pb.ex:39-56 | lib/_generated/spawn/actors/healthcheck.pb.ex:80-97 | lib/_generated/spawn/actors/healthcheck.pb.ex:158-175 | lib/_generated/spawn/actors/healthcheck.pb.ex:186-203 | lib/_generated/spawn/actors/protocol.pb.ex:465-482 | lib/_generated/spawn/actors/protocol.pb.ex:519-536 | lib/_generated/spawn/actors/protocol.pb.ex:727-744 | lib/_generated/spawn/actors/protocol.pb.ex:850-867 | lib/_generated/spawn/actors/protocol.pb.ex:1781-1798 | lib/_generated/spawn/actors/state.pb.ex:64-81 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (18 lines × 11) lib/_generated/io/cloudevents/v1/spec.pb.ex:263— lib/_generated/io/cloudevents/v1/spec.pb.ex:263-280 | lib/_generated/spawn/actors/actor.pb.ex:578-595 | lib/_generated/spawn/actors/actor.pb.ex:749-766 | lib/_generated/spawn/actors/actor.pb.ex:1056-1073 | lib/_generated/spawn/actors/actor.pb.ex:1428-1445 | lib/_generated/spawn/actors/extensions.pb.ex:131-148 | lib/_generated/spawn/actors/protocol.pb.ex:199-216 | lib/_generated/spawn/actors/protocol.pb.ex:1195-1212 | lib/_generated/spawn/actors/protocol.pb.ex:1318-1335 | lib/_generated/spawn/actors/protocol.pb.ex:1558-1575 | lib/_generated/spawn/actors/test.pb.ex:470-487 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (17–18 lines × 9) lib/_generated/spawn/actors/actor.pb.ex:1066— lib/_generated/spawn/actors/actor.pb.ex:1066-1082 | lib/_generated/spawn/actors/actor.pb.ex:1094-1111 | lib/_generated/spawn/actors/actor.pb.ex:1155-1171 | lib/_generated/spawn/actors/extensions.pb.ex:43-59 | lib/_generated/spawn/actors/extensions.pb.ex:85-101 | lib/_generated/spawn/actors/protocol.pb.ex:1526-1542 | lib/_generated/spawn/actors/protocol.pb.ex:1582-1598 | lib/_generated/spawn/actors/protocol.pb.ex:1912-1929 | lib/_generated/spawn/actors/test.pb.ex:382-398 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/extensions.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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 × 5) lib/_generated/spawn/actors/actor.pb.ex:593— lib/_generated/spawn/actors/actor.pb.ex:593-610 | lib/_generated/spawn/actors/protocol.pb.ex:242-259 | lib/_generated/spawn/actors/protocol.pb.ex:1210-1227 | lib/_generated/spawn/actors/test.pb.ex:161-178 | lib/_generated/spawn/actors/test.pb.ex:560-577 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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–18 lines × 5) lib/_generated/spawn/actors/healthcheck.pb.ex:325— lib/_generated/spawn/actors/healthcheck.pb.ex:325-338 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:251-268 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:283-300 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:116-133 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:148-165 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 327 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 (18 lines × 4) lib/_generated/spawn/actors/actor.pb.ex:40— lib/_generated/spawn/actors/actor.pb.ex:40-57 | lib/_generated/spawn/actors/protocol.pb.ex:22-39 | lib/_generated/spawn/actors/test.pb.ex:16-33 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:10-27 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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–18 lines × 3) lib/_generated/spawn/actors/healthcheck.pb.ex:173— lib/_generated/spawn/actors/healthcheck.pb.ex:173-189 | lib/_generated/spawn/actors/test.pb.ex:617-634 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:110-126 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `lib/_generated/spawn/actors/test.pb.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 169 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–18 lines × 2) lib/_generated/io/cloudevents/v1/spec.pb.ex:486— lib/_generated/io/cloudevents/v1/spec.pb.ex:486-500 | lib/_generated/spawn/actors/protocol.pb.ex:1664-1681 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 381 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 (16–17 lines × 40) lib/_generated/io/cloudevents/v1/spec.pb.ex:7— lib/_generated/io/cloudevents/v1/spec.pb.ex:7-22 | lib/_generated/io/cloudevents/v1/spec.pb.ex:204-219 | lib/_generated/io/cloudevents/v1/spec.pb.ex:321-336 | lib/_generated/spawn/actors/actor.pb.ex:75-90 | lib/_generated/spawn/actors/actor.pb.ex:158-173 | lib/_generated/spawn/actors/actor.pb.ex:231-246 | lib/_generated/spawn/actors/actor.pb.ex:418-434 | lib/_generated/spawn/actors/actor.pb.ex:511-526 | lib/_generated/spawn/actors/actor.pb.ex:608-623 | lib/_generated/spawn/actors/actor.pb.ex:682-697 | lib/_generated/spawn/actors/actor.pb.ex:779-794 | lib/_generated/spawn/actors/actor.pb.ex:853-868 | lib/_generated/spawn/actors/actor.pb.ex:907-922 | lib/_generated/spawn/actors/actor.pb.ex:1300-1315 | lib/_generated/spawn/actors/extensions.pb.ex:30-45 | lib/_generated/spawn/actors/extensions.pb.ex:194-209 | lib/_generated/spawn/actors/healthcheck.pb.ex:7-22 | lib/_generated/spawn/actors/healthcheck.pb.ex:126-141 | lib/_generated/spawn/actors/protocol.pb.ex:54-69 | lib/_generated/spawn/actors/protocol.pb.ex:118-133 | lib/_generated/spawn/actors/protocol.pb.ex:257-272 | lib/_generated/spawn/actors/protocol.pb.ex:309-324 | lib/_generated/spawn/actors/protocol.pb.ex:408-424 | lib/_generated/spawn/actors/protocol.pb.ex:555-570 | lib/_generated/spawn/actors/protocol.pb.ex:885-900 | lib/_generated/spawn/actors/protocol.pb.ex:962-977 | lib/_generated/spawn/actors/protocol.pb.ex:1031-1046 | lib/_generated/spawn/actors/protocol.pb.ex:1100-1115 | lib/_generated/spawn/actors/protocol.pb.ex:1164-1179 | lib/_generated/spawn/actors/protocol.pb.ex:1225-1240 | lib/_generated/spawn/actors/protocol.pb.ex:1393-1408 | lib/_generated/spawn/actors/protocol.pb.ex:1616-1631 | lib/_generated/spawn/actors/protocol.pb.ex:1829-1844 | lib/_generated/spawn/actors/test.pb.ex:47-62 | lib/_generated/spawn/actors/test.pb.ex:101-116 | lib/_generated/spawn/actors/test.pb.ex:176-191 | lib/_generated/spawn/actors/test.pb.ex:243-258 | lib/_generated/spawn/actors/test.pb.ex:500-515 | lib/_generated/spawn/actors/test.pb.ex:575-590 | lib/_generated/spawn/actors/test.pb.ex:627-642 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (15–17 lines × 15) lib/_generated/spawn/actors/healthcheck.pb.ex:408— lib/_generated/spawn/actors/healthcheck.pb.ex:408-422 | lib/_generated/spawn/actors/healthcheck.pb.ex:440-454 | lib/_generated/spawn/actors/healthcheck.pb.ex:472-486 | lib/_generated/spawn/actors/healthcheck.pb.ex:520-534 | lib/_generated/spawn/actors/healthcheck.pb.ex:586-602 | lib/_generated/spawn/actors/healthcheck.pb.ex:633-647 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:154-168 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:185-199 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:233-247 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:339-353 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:387-401 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:436-450 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:484-498 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:205-219 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:253-267 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (16–17 lines × 13) lib/_generated/spawn/actors/actor.pb.ex:1369— lib/_generated/spawn/actors/actor.pb.ex:1369-1384 | lib/_generated/spawn/actors/healthcheck.pb.ex:76-92 | lib/_generated/spawn/actors/healthcheck.pb.ex:182-198 | lib/_generated/spawn/actors/protocol.pb.ex:182-197 | lib/_generated/spawn/actors/protocol.pb.ex:447-462 | lib/_generated/spawn/actors/protocol.pb.ex:501-516 | lib/_generated/spawn/actors/protocol.pb.ex:723-739 | lib/_generated/spawn/actors/protocol.pb.ex:846-862 | lib/_generated/spawn/actors/protocol.pb.ex:1301-1316 | lib/_generated/spawn/actors/protocol.pb.ex:1457-1472 | lib/_generated/spawn/actors/protocol.pb.ex:1707-1722 | lib/_generated/spawn/actors/protocol.pb.ex:1966-1981 | lib/_generated/spawn/actors/state.pb.ex:46-61 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/healthcheck.pb.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 189 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 × 11) lib/_generated/io/cloudevents/v1/spec.pb.ex:315— lib/_generated/io/cloudevents/v1/spec.pb.ex:315-331 | lib/_generated/spawn/actors/actor.pb.ex:152-168 | lib/_generated/spawn/actors/actor.pb.ex:602-618 | lib/_generated/spawn/actors/actor.pb.ex:773-789 | lib/_generated/spawn/actors/protocol.pb.ex:251-267 | lib/_generated/spawn/actors/protocol.pb.ex:1219-1235 | lib/_generated/spawn/actors/protocol.pb.ex:1610-1626 | lib/_generated/spawn/actors/test.pb.ex:170-186 | lib/_generated/spawn/actors/test.pb.ex:494-510 | lib/_generated/spawn/actors/test.pb.ex:569-585 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:267-283 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (16–17 lines × 9) lib/_generated/spawn/actors/actor.pb.ex:457— lib/_generated/spawn/actors/actor.pb.ex:457-472 | lib/_generated/spawn/actors/protocol.pb.ex:762-777 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:40-55 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:202-217 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:350-366 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:7-23 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:46-62 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:91-107 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:119-135 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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–17 lines × 6) lib/_generated/spawn/actors/actor.pb.ex:139— lib/_generated/spawn/actors/actor.pb.ex:139-155 | lib/_generated/spawn/actors/actor.pb.ex:575-590 | lib/_generated/spawn/actors/actor.pb.ex:746-761 | lib/_generated/spawn/actors/actor.pb.ex:1053-1068 | lib/_generated/spawn/actors/protocol.pb.ex:684-700 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:389-405 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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–17 lines × 4) lib/_generated/spawn/actors/healthcheck.pb.ex:224— lib/_generated/spawn/actors/healthcheck.pb.ex:224-239 | lib/_generated/spawn/actors/healthcheck.pb.ex:249-265 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:160-175 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:25-40 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 327 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 (17 lines × 3) lib/_generated/spawn/actors/healthcheck.pb.ex:559— lib/_generated/spawn/actors/healthcheck.pb.ex:559-575 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:128-144 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:159-175 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (16 lines × 32) lib/_generated/io/cloudevents/v1/spec.pb.ex:17— lib/_generated/io/cloudevents/v1/spec.pb.ex:17-32 | lib/_generated/io/cloudevents/v1/spec.pb.ex:331-346 | lib/_generated/spawn/actors/actor.pb.ex:85-100 | lib/_generated/spawn/actors/actor.pb.ex:168-183 | lib/_generated/spawn/actors/actor.pb.ex:241-256 | lib/_generated/spawn/actors/actor.pb.ex:467-482 | lib/_generated/spawn/actors/actor.pb.ex:585-600 | lib/_generated/spawn/actors/actor.pb.ex:945-960 | lib/_generated/spawn/actors/actor.pb.ex:1077-1092 | lib/_generated/spawn/actors/actor.pb.ex:1166-1181 | lib/_generated/spawn/actors/actor.pb.ex:1222-1237 | lib/_generated/spawn/actors/actor.pb.ex:1379-1394 | lib/_generated/spawn/actors/extensions.pb.ex:110-125 | lib/_generated/spawn/actors/healthcheck.pb.ex:31-46 | lib/_generated/spawn/actors/healthcheck.pb.ex:150-165 | lib/_generated/spawn/actors/protocol.pb.ex:220-235 | lib/_generated/spawn/actors/protocol.pb.ex:457-472 | lib/_generated/spawn/actors/protocol.pb.ex:511-526 | lib/_generated/spawn/actors/protocol.pb.ex:895-910 | lib/_generated/spawn/actors/protocol.pb.ex:1174-1189 | lib/_generated/spawn/actors/protocol.pb.ex:1202-1217 | lib/_generated/spawn/actors/protocol.pb.ex:1325-1340 | lib/_generated/spawn/actors/protocol.pb.ex:1467-1482 | lib/_generated/spawn/actors/protocol.pb.ex:1495-1510 | lib/_generated/spawn/actors/protocol.pb.ex:1537-1552 | lib/_generated/spawn/actors/protocol.pb.ex:1731-1746 | lib/_generated/spawn/actors/protocol.pb.ex:1853-1868 | lib/_generated/spawn/actors/protocol.pb.ex:1976-1991 | lib/_generated/spawn/actors/state.pb.ex:56-71 | lib/_generated/spawn/actors/test.pb.ex:153-168 | lib/_generated/spawn/actors/test.pb.ex:407-422 | lib/_generated/spawn/actors/test.pb.ex:552-567 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (15–16 lines × 30) lib/_generated/spawn/actors/actor.pb.ex:421— lib/_generated/spawn/actors/actor.pb.ex:421-435 | lib/_generated/spawn/actors/actor.pb.ex:528-542 | lib/_generated/spawn/actors/actor.pb.ex:625-639 | lib/_generated/spawn/actors/actor.pb.ex:699-713 | lib/_generated/spawn/actors/actor.pb.ex:796-810 | lib/_generated/spawn/actors/actor.pb.ex:870-884 | lib/_generated/spawn/actors/actor.pb.ex:1243-1257 | lib/_generated/spawn/actors/actor.pb.ex:1331-1345 | lib/_generated/spawn/actors/protocol.pb.ex:71-85 | lib/_generated/spawn/actors/protocol.pb.ex:135-149 | lib/_generated/spawn/actors/protocol.pb.ex:274-288 | lib/_generated/spawn/actors/protocol.pb.ex:326-340 | lib/_generated/spawn/actors/protocol.pb.ex:411-425 | lib/_generated/spawn/actors/protocol.pb.ex:807-821 | lib/_generated/spawn/actors/protocol.pb.ex:993-1007 | lib/_generated/spawn/actors/protocol.pb.ex:1062-1076 | lib/_generated/spawn/actors/protocol.pb.ex:1117-1131 | lib/_generated/spawn/actors/protocol.pb.ex:1242-1256 | lib/_generated/spawn/actors/protocol.pb.ex:1410-1424 | lib/_generated/spawn/actors/protocol.pb.ex:1600-1615 | lib/_generated/spawn/actors/protocol.pb.ex:1633-1647 | lib/_generated/spawn/actors/protocol.pb.ex:2090-2104 | lib/_generated/spawn/actors/test.pb.ex:64-78 | lib/_generated/spawn/actors/test.pb.ex:193-207 | lib/_generated/spawn/actors/test.pb.ex:260-274 | lib/_generated/spawn/actors/test.pb.ex:592-606 | lib/_generated/spawn/actors/test.pb.ex:644-658 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:97-111 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:165-179 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:302-316 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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–16 lines × 22) lib/_generated/io/cloudevents/v1/spec.pb.ex:24— lib/_generated/io/cloudevents/v1/spec.pb.ex:24-38 | lib/_generated/io/cloudevents/v1/spec.pb.ex:338-352 | lib/_generated/spawn/actors/actor.pb.ex:92-106 | lib/_generated/spawn/actors/actor.pb.ex:175-189 | lib/_generated/spawn/actors/actor.pb.ex:248-262 | lib/_generated/spawn/actors/actor.pb.ex:474-488 | lib/_generated/spawn/actors/actor.pb.ex:592-607 | lib/_generated/spawn/actors/actor.pb.ex:952-966 | lib/_generated/spawn/actors/healthcheck.pb.ex:38-52 | lib/_generated/spawn/actors/healthcheck.pb.ex:79-93 | lib/_generated/spawn/actors/healthcheck.pb.ex:157-171 | lib/_generated/spawn/actors/healthcheck.pb.ex:185-199 | lib/_generated/spawn/actors/protocol.pb.ex:241-256 | lib/_generated/spawn/actors/protocol.pb.ex:464-478 | lib/_generated/spawn/actors/protocol.pb.ex:518-532 | lib/_generated/spawn/actors/protocol.pb.ex:726-740 | lib/_generated/spawn/actors/protocol.pb.ex:849-863 | lib/_generated/spawn/actors/protocol.pb.ex:1209-1224 | lib/_generated/spawn/actors/protocol.pb.ex:1780-1794 | lib/_generated/spawn/actors/state.pb.ex:63-77 | lib/_generated/spawn/actors/test.pb.ex:160-175 | lib/_generated/spawn/actors/test.pb.ex:559-574 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (15–16 lines × 16) lib/_generated/spawn/actors/actor.pb.ex:253— lib/_generated/spawn/actors/actor.pb.ex:253-267 | lib/_generated/spawn/actors/actor.pb.ex:479-493 | lib/_generated/spawn/actors/actor.pb.ex:957-971 | lib/_generated/spawn/actors/actor.pb.ex:1447-1461 | lib/_generated/spawn/actors/healthcheck.pb.ex:43-57 | lib/_generated/spawn/actors/healthcheck.pb.ex:84-98 | lib/_generated/spawn/actors/healthcheck.pb.ex:162-176 | lib/_generated/spawn/actors/healthcheck.pb.ex:190-204 | lib/_generated/spawn/actors/protocol.pb.ex:469-483 | lib/_generated/spawn/actors/protocol.pb.ex:523-537 | lib/_generated/spawn/actors/protocol.pb.ex:692-706 | lib/_generated/spawn/actors/protocol.pb.ex:731-745 | lib/_generated/spawn/actors/protocol.pb.ex:854-868 | lib/_generated/spawn/actors/protocol.pb.ex:1785-1800 | lib/_generated/spawn/actors/state.pb.ex:68-82 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:397-411 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/healthcheck.pb.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 189 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–16 lines × 12) lib/_generated/io/cloudevents/v1/spec.pb.ex:174— lib/_generated/io/cloudevents/v1/spec.pb.ex:174-184 | lib/_generated/io/cloudevents/v1/spec.pb.ex:476-490 | lib/_generated/io/cloudevents/v1/spec.pb.ex:491-502 | lib/_generated/spawn/actors/actor.pb.ex:304-318 | lib/_generated/spawn/actors/actor.pb.ex:351-365 | lib/_generated/spawn/actors/actor.pb.ex:1024-1038 | lib/_generated/spawn/actors/protocol.pb.ex:932-946 | lib/_generated/spawn/actors/protocol.pb.ex:1362-1376 | lib/_generated/spawn/actors/protocol.pb.ex:1668-1683 | lib/_generated/spawn/actors/protocol.pb.ex:1796-1810 | lib/_generated/spawn/actors/protocol.pb.ex:1932-1946 | lib/_generated/spawn/actors/protocol.pb.ex:2041-2055 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (15–16 lines × 8) lib/_generated/io/cloudevents/v1/spec.pb.ex:158— lib/_generated/io/cloudevents/v1/spec.pb.ex:158-172 | lib/_generated/io/cloudevents/v1/spec.pb.ex:305-320 | lib/_generated/io/cloudevents/v1/spec.pb.ex:460-474 | lib/_generated/spawn/actors/actor.pb.ex:288-302 | lib/_generated/spawn/actors/actor.pb.ex:335-349 | lib/_generated/spawn/actors/protocol.pb.ex:916-930 | lib/_generated/spawn/actors/protocol.pb.ex:1346-1360 | lib/_generated/spawn/actors/protocol.pb.ex:2025-2039 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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–16 lines × 7) lib/_generated/spawn/actors/healthcheck.pb.ex:568— lib/_generated/spawn/actors/healthcheck.pb.ex:568-583 | lib/_generated/spawn/actors/healthcheck.pb.ex:624-632 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:137-152 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:168-183 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:224-232 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:475-483 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:244-252 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (15–16 lines × 5) lib/_generated/spawn/actors/actor.pb.ex:142— lib/_generated/spawn/actors/actor.pb.ex:142-157 | lib/_generated/spawn/actors/actor.pb.ex:763-778 | lib/_generated/spawn/actors/actor.pb.ex:1442-1456 | lib/_generated/spawn/actors/protocol.pb.ex:687-701 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:392-406 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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 × 39) lib/_generated/io/cloudevents/v1/spec.pb.ex:214— lib/_generated/io/cloudevents/v1/spec.pb.ex:214-228 | lib/_generated/spawn/actors/actor.pb.ex:521-535 | lib/_generated/spawn/actors/actor.pb.ex:618-632 | lib/_generated/spawn/actors/actor.pb.ex:692-706 | lib/_generated/spawn/actors/actor.pb.ex:789-803 | lib/_generated/spawn/actors/actor.pb.ex:863-877 | lib/_generated/spawn/actors/actor.pb.ex:917-931 | lib/_generated/spawn/actors/actor.pb.ex:1236-1250 | lib/_generated/spawn/actors/actor.pb.ex:1310-1324 | lib/_generated/spawn/actors/extensions.pb.ex:204-218 | lib/_generated/spawn/actors/healthcheck.pb.ex:17-31 | lib/_generated/spawn/actors/healthcheck.pb.ex:136-150 | lib/_generated/spawn/actors/protocol.pb.ex:64-78 | lib/_generated/spawn/actors/protocol.pb.ex:128-142 | lib/_generated/spawn/actors/protocol.pb.ex:267-281 | lib/_generated/spawn/actors/protocol.pb.ex:319-333 | lib/_generated/spawn/actors/protocol.pb.ex:565-579 | lib/_generated/spawn/actors/protocol.pb.ex:786-800 | lib/_generated/spawn/actors/protocol.pb.ex:972-986 | lib/_generated/spawn/actors/protocol.pb.ex:1041-1055 | lib/_generated/spawn/actors/protocol.pb.ex:1110-1124 | lib/_generated/spawn/actors/protocol.pb.ex:1235-1249 | lib/_generated/spawn/actors/protocol.pb.ex:1403-1417 | lib/_generated/spawn/actors/protocol.pb.ex:1481-1495 | lib/_generated/spawn/actors/protocol.pb.ex:1593-1607 | lib/_generated/spawn/actors/protocol.pb.ex:1626-1640 | lib/_generated/spawn/actors/protocol.pb.ex:1717-1731 | lib/_generated/spawn/actors/protocol.pb.ex:1839-1853 | lib/_generated/spawn/actors/protocol.pb.ex:2083-2097 | lib/_generated/spawn/actors/test.pb.ex:57-71 | lib/_generated/spawn/actors/test.pb.ex:111-125 | lib/_generated/spawn/actors/test.pb.ex:186-200 | lib/_generated/spawn/actors/test.pb.ex:253-267 | lib/_generated/spawn/actors/test.pb.ex:510-524 | lib/_generated/spawn/actors/test.pb.ex:585-599 | lib/_generated/spawn/actors/test.pb.ex:637-651 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:50-64 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:90-104 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:212-226 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 (15 lines × 9) lib/_generated/io/cloudevents/v1/spec.pb.ex:267— lib/_generated/io/cloudevents/v1/spec.pb.ex:267-281 | lib/_generated/spawn/actors/actor.pb.ex:582-596 | lib/_generated/spawn/actors/actor.pb.ex:1060-1074 | lib/_generated/spawn/actors/extensions.pb.ex:135-149 | lib/_generated/spawn/actors/protocol.pb.ex:217-231 | lib/_generated/spawn/actors/protocol.pb.ex:1199-1213 | lib/_generated/spawn/actors/protocol.pb.ex:1322-1336 | lib/_generated/spawn/actors/protocol.pb.ex:1562-1576 | lib/_generated/spawn/actors/test.pb.ex:474-488 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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–15 lines × 9) lib/_generated/spawn/actors/actor.pb.ex:205— lib/_generated/spawn/actors/actor.pb.ex:205-219 | lib/_generated/spawn/actors/actor.pb.ex:655-669 | lib/_generated/spawn/actors/actor.pb.ex:826-840 | lib/_generated/spawn/actors/protocol.pb.ex:356-370 | lib/_generated/spawn/actors/protocol.pb.ex:1272-1286 | lib/_generated/spawn/actors/test.pb.ex:213-227 | lib/_generated/spawn/actors/test.pb.ex:612-625 | lib/_generated/spawn/actors/test.pb.ex:674-688 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:322-336 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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 × 7) lib/_generated/spawn/actors/actor.pb.ex:1418— lib/_generated/spawn/actors/actor.pb.ex:1418-1432 | lib/_generated/spawn/actors/extensions.pb.ex:121-135 | lib/_generated/spawn/actors/protocol.pb.ex:189-203 | lib/_generated/spawn/actors/protocol.pb.ex:1185-1199 | lib/_generated/spawn/actors/protocol.pb.ex:1308-1322 | lib/_generated/spawn/actors/protocol.pb.ex:1548-1562 | lib/_generated/spawn/actors/test.pb.ex:446-460 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/extensions.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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–15 lines × 4) lib/_generated/spawn/actors/actor.pb.ex:7— lib/_generated/spawn/actors/actor.pb.ex:7-20 | lib/_generated/spawn/actors/protocol.pb.ex:7-20 | lib/_generated/spawn/actors/test.pb.ex:7-20 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:7-21 — before extracting anything, compare `lib/_generated/spawn/actors/actor.pb.ex` and `lib/_generated/spawn/actors/protocol.pb.ex` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 732 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 × 4) lib/_generated/spawn/actors/healthcheck.pb.ex:648— lib/_generated/spawn/actors/healthcheck.pb.ex:648-662 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:355-369 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:395-409 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:212-226 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 327 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 (15 lines × 3) spawnctl/lib/spawnctl/commands/new/elixir.ex:144— spawnctl/lib/spawnctl/commands/new/elixir.ex:144-158 | spawnctl/lib/spawnctl/commands/new/java.ex:128-142 | spawnctl/lib/spawnctl/commands/new/node.ex:117-131 — before extracting anything, compare `spawnctl/lib/spawnctl/commands/new/java.ex` and `spawnctl/lib/spawnctl/commands/new/node.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 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) lib/actors/actor/state_manager.ex:43— lib/actors/actor/state_manager.ex:43-57 | lib/actors/actor/state_manager.ex:69-83 — 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 × 23) lib/_generated/io/cloudevents/v1/spec.pb.ex:268— lib/_generated/io/cloudevents/v1/spec.pb.ex:268-281 | lib/_generated/spawn/actors/actor.pb.ex:583-596 | lib/_generated/spawn/actors/actor.pb.ex:1061-1074 | lib/_generated/spawn/actors/actor.pb.ex:1089-1102 | lib/_generated/spawn/actors/actor.pb.ex:1178-1191 | lib/_generated/spawn/actors/actor.pb.ex:1234-1247 | lib/_generated/spawn/actors/actor.pb.ex:1377-1390 | lib/_generated/spawn/actors/extensions.pb.ex:136-149 | lib/_generated/spawn/actors/protocol.pb.ex:218-231 | lib/_generated/spawn/actors/protocol.pb.ex:455-468 | lib/_generated/spawn/actors/protocol.pb.ex:509-522 | lib/_generated/spawn/actors/protocol.pb.ex:1200-1213 | lib/_generated/spawn/actors/protocol.pb.ex:1323-1336 | lib/_generated/spawn/actors/protocol.pb.ex:1465-1478 | lib/_generated/spawn/actors/protocol.pb.ex:1563-1576 | lib/_generated/spawn/actors/protocol.pb.ex:1715-1728 | lib/_generated/spawn/actors/protocol.pb.ex:1743-1756 | lib/_generated/spawn/actors/protocol.pb.ex:1865-1878 | lib/_generated/spawn/actors/protocol.pb.ex:1907-1920 | lib/_generated/spawn/actors/protocol.pb.ex:1974-1987 | lib/_generated/spawn/actors/state.pb.ex:54-67 | lib/_generated/spawn/actors/test.pb.ex:419-432 | lib/_generated/spawn/actors/test.pb.ex:475-488 — before extracting anything, compare `lib/_generated/io/cloudevents/v1/spec.pb.ex` and `lib/_generated/spawn/actors/actor.pb.ex` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 322 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 × 2) spawn_operator/spawn_operator/lib/spawn_operator/k8s/system/headless_service.ex:21— spawn_operator/spawn_operator/lib/spawn_operator/k8s/system/headless_service.ex:21-34 | spawn_operator/spawn_operator/lib/spawn_operator/k8s/system/role_binding.ex:17-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 (13 lines × 9) lib/_generated/spawn/actors/healthcheck.pb.ex:394— lib/_generated/spawn/actors/healthcheck.pb.ex:394-406 | lib/_generated/spawn/actors/healthcheck.pb.ex:506-518 | lib/_generated/spawn/actors/healthcheck.pb.ex:554-566 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:123-135 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:154-166 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:325-337 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:373-385 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:421-433 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:190-202 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 × 5) lib/_generated/spawn/actors/healthcheck.pb.ex:210— lib/_generated/spawn/actors/healthcheck.pb.ex:210-222 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:15-26 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:15-26 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:147-159 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:13-24 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (11 lines × 3) spawnctl/lib/spawnctl/commands/new/elixir.ex:168— spawnctl/lib/spawnctl/commands/new/elixir.ex:168-178 | spawnctl/lib/spawnctl/commands/new/java.ex:152-162 | spawnctl/lib/spawnctl/commands/new/node.ex:141-151 — before extracting anything, compare `spawnctl/lib/spawnctl/commands/new/java.ex` and `spawnctl/lib/spawnctl/commands/new/node.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 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 × 9) lib/_generated/spawn/actors/healthcheck.pb.ex:341— lib/_generated/spawn/actors/healthcheck.pb.ex:341-350 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:78-87 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:109-118 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:240-249 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:272-281 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:296-305 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:105-114 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:137-146 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:161-170 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 × 6) lib/_generated/spawn/actors/healthcheck.pb.ex:352— lib/_generated/spawn/actors/healthcheck.pb.ex:352-360 | lib/_generated/spawn/actors/healthcheck.pb.ex:496-504 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:89-97 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:120-128 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:307-315 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:172-180 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 × 5) lib/_generated/spawn/actors/healthcheck.pb.ex:384— lib/_generated/spawn/actors/healthcheck.pb.ex:384-392 | lib/_generated/spawn/actors/healthcheck.pb.ex:544-552 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:113-121 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:144-152 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:180-188 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (8 lines × 8) lib/_generated/spawn/actors/healthcheck.pb.ex:400— lib/_generated/spawn/actors/healthcheck.pb.ex:400-407 | lib/_generated/spawn/actors/healthcheck.pb.ex:432-439 | lib/_generated/spawn/actors/healthcheck.pb.ex:464-471 | lib/_generated/spawn/actors/healthcheck.pb.ex:512-519 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:331-338 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:379-386 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:427-434 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:196-203 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 327 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 (8 lines × 3) spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:495— spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:495-502 | spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:527-534 | spawn_operator/spawn_operator/lib/spawn_operator/k8s/proxy/deployment.ex:561-568 — 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 (7 lines × 17) lib/_generated/spawn/actors/healthcheck.pb.ex:616— lib/_generated/spawn/actors/healthcheck.pb.ex:616-622 | lib/_generated/spawn/actors/healthcheck.pb.ex:632-638 | lib/_generated/spawn/actors/healthcheck.pb.ex:664-670 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:153-159 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:185-191 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:184-190 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:216-222 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:232-238 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:264-270 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:435-441 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:467-473 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:483-489 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:515-521 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:204-210 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:236-242 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:252-258 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:284-290 — before extracting anything, compare `lib/_generated/spawn/actors/healthcheck.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 239 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 (36 lines × 2) lib/actors/k8s/k8s_conn.ex:8— lib/actors/k8s/k8s_conn.ex:8-43 | spawn_initializer/lib/spawn_initializer/k8s/k8s_conn.ex:8-43 — 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.
Near-duplicate member pair (104 shared lines) lib/_generated/io/cloudevents/v1/spec.pb.ex:71— lib/_generated/io/cloudevents/v1/spec.pb.ex:71-184 | lib/_generated/io/cloudevents/v1/spec.pb.ex:204-502 — These two members are variants of one another: 104 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.
Duplicated block (55 lines × 2) lib/_generated/io/cloudevents/v1/spec.pb.ex:71— lib/_generated/io/cloudevents/v1/spec.pb.ex:71-125 | lib/_generated/io/cloudevents/v1/spec.pb.ex:373-427 — 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 (49 lines × 2) spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:187— spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:187-235 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:52-100 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 386 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 (24 lines × 4) spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:61— spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:61-84 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:143-166 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:223-246 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:280-303 — 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 (21 lines × 3) lib/_generated/spawn/actors/test.pb.ex:205— lib/_generated/spawn/actors/test.pb.ex:205-225 | lib/_generated/spawn/actors/test.pb.ex:604-624 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:314-334 — before extracting anything, compare `lib/_generated/spawn/actors/test.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 221 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 (20 lines × 3) spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:25— spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:25-44 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:182-201 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:47-66 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 243 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 (16 lines × 3) spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:35— spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:35-50 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:170-185 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:35-50 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 225 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–15 lines × 3) spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:11— spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:11-25 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:11-25 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:12-23 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 365 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 × 5) spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:20— spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:20-33 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:153-166 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:177-190 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:18-31 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:42-55 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 243 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 × 4) spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:15— spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:15-28 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:15-28 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/example.pb.ex:148-161 | spawn_sdk/spawn_sdk_example/lib/spawn_sdk_example/actors/inside_folder/clock.pb.ex:13-26 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 365 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) spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:64— spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:64-74 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:146-156 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:226-236 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:252-262 | spawn_sdk/spawn_sdk_example/lib/_generated/example/example.pb.ex:283-293 — 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 (10 lines × 3) spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:236— spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex:236-245 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:326-335 | spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex:340-349 — before extracting anything, compare `spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex` and `spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 365 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.
Off the main sequence: spawn_statestores — spawn_statestores: abstractness 0.21, instability 0.00, distance 0.79 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
README/code drift README.md:226— README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
README/code drift docs/local_development.md:17— docs/local_development.md links to `CONTRIBUTING.md`, but `docs/CONTRIBUTING.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 docs/overview.md:9— docs/overview.md links to `docs/index.md`, but `docs/docs/index.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 docs/overview.md:9— docs/overview.md links to `docs/getting_started.md`, but `docs/docs/getting_started.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 docs/statestores.md:4— docs/statestores.md links to `docs/getting_started.md`, but `docs/docs/getting_started.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 tools/sdk-init/README.md:63— tools/sdk-init/README.md documents the environment variable `GOOS`, but no code, script or configuration file names it. 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 tools/sdk-init/README.md:63— tools/sdk-init/README.md documents the environment variable `GOARCH`, but no code, script or configuration file names it. 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 tools/sdk-init/README.md:63— tools/sdk-init/README.md documents the environment variable `CGO_ENABLED`, but no code, script or configuration file names it. 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.
Orphaned file spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.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 spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.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 lib/sidecar/grpc/generators/actor_invoker_generator.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 lib/actors/actor/invocation_scheduler.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 lib/spawn/cluster/state_handoff/controllers/nats_kv_controller.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 lib/spawn/cluster/state_handoff/invocation_scheduler_state.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 spawn_sdk/spawn_sdk/lib/defact.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.
Duplicated predicate spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex:310— `String.match?(token, ~r/\bLIMIT\b|\bOFFSET\b/i) and depth == 0` appears character-identically in 2 files — spawn_statestores/statestores_mariadb/lib/statestores/adapters/mariadb_projection_adapter.ex, spawn_statestores/statestores_postgres/lib/statestores/adapters/postgres_projection_adapter.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 spawn_operator/spawn_operator/lib/spawn_operator/routes/base.ex:18— `is_integer(code) and content_type == "application/json"` appears character-identically in 2 files — spawn_operator/spawn_operator/lib/spawn_operator/routes/base.ex, spawn_proxy/proxy/lib/proxy/routes/base.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 spawnctl/lib/spawnctl/commands/new/elixir.ex:200— `is_nil(opts.statestore_type) || opts.statestore_type == ""` appears character-identically in 2 files — spawnctl/lib/spawnctl/commands/new/elixir.ex, spawnctl/lib/spawnctl/commands/new/java.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 lib/actors/k8s/k8s_conn.ex:29— `not is_nil(kubeconfig) and File.exists?(kubeconfig)` appears character-identically in 2 files — lib/actors/k8s/k8s_conn.ex, spawn_initializer/lib/spawn_initializer/k8s/k8s_conn.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 lib/actors/actor/caller_consumer.ex:139— `request.register_ref != "" and not is_nil(request.register_ref)` appears character-identically in 2 files — lib/actors/actor/caller_consumer.ex, lib/actors/actor/caller_producer.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 lib/spawn/cluster/cluster_supervisor.ex:51— `topologies && Code.ensure_compiled(Cluster.Supervisor)` appears character-identically in 2 files — lib/spawn/cluster/cluster_supervisor.ex, spawn_monitor/lib/spawn_monitor/cluster.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.
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:36— 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:82— 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 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/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 13 project(s) overshoot their size bounds, lowering Project Cohesion to 8.5/10. The most over is `(repository root)` (13939 LoC, 146 module-visible types across 31 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 7 of 82 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 82 of the 302 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: spawn_sdk/spawn_sdk_example/lib/_generated/actors/projection_actor.pb.ex, spawn_sdk/spawn_sdk_example/lib/_generated/actors/example.pb.ex, lib/sidecar/grpc/generators/actor_invoker_generator.ex, lib/actors/actor/invocation_scheduler.ex, lib/spawn/cluster/state_handoff/invocation_scheduler_state.ex, spawn_sdk/spawn_sdk/lib/defact.ex, lib/spawn/cluster/state_handoff/controllers/nats_kv_controller.ex. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No 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.
Logging is not universal — Only 10/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `spawnctl`.
No SAST — No static application security testing detected. For this repository's stack, add sobelow (Elixir/Phoenix) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 10879 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
Benchmarks don't track allocations spawn_sdk/spawn_sdk_example/benchmark.exs— A Elixir Benchee/Benchfella suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
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: spawn_monitor/lib/spawn_monitor_web/endpoint.ex:3 — `Phoenix.Endpoint`.
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Elixir server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: spawn_monitor/lib/spawn_monitor_web/endpoint.ex:3 — `Phoenix.Endpoint`.
Outdated: bandit — `:bandit` is locked at 1.5.3 but 1.13.1 is the current stable release on hex.pm, and it already satisfies the `"~> 1.5"` requirement declared in spawn_operator/spawn_operator/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update bandit` and commit the updated REDACTED.
Outdated: benchee — `:benchee` is locked at 1.1.0 but 1.5.1 is the current stable release on hex.pm, and it already satisfies the `"~> 1.0"` requirement declared in spawn_sdk/spawn_sdk_example/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update benchee` and commit the updated REDACTED.
Outdated: benchee_html — `:benchee_html` is locked at 1.0.0 but 1.0.1 is the current stable release on hex.pm, and it already satisfies the `"~> 1.0"` requirement declared in spawn_sdk/spawn_sdk_example/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update benchee_html` and commit the updated REDACTED.
Outdated: bonny — `:bonny` is locked at 1.4.0 but 1.5.0 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in spawn_operator/spawn_operator/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update bonny` 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.1"` requirement declared in mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update broadway` and commit the updated REDACTED.
Outdated: broadway_dashboard — `:broadway_dashboard` is locked at 0.4.1 but 0.5.0 is the current stable release on hex.pm, and it already satisfies the `"~> 0.4"` requirement declared in spawn_monitor/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update broadway_dashboard` and commit the updated REDACTED.
Outdated: burrito — `:burrito` is locked at 1.1.0 but 1.6.0 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in spawnctl/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update burrito` and commit the updated REDACTED.
Outdated: castore — `:castore` is locked at 1.0.12 but 1.0.22 is the current stable release on hex.pm, and it already satisfies the `"~> 1.0"` requirement declared in spawn_operator/spawn_operator/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update castore` and commit the updated REDACTED.
Outdated: castore — `:castore` is locked at 1.0.17 but 1.0.22 is the current stable release on hex.pm, and it already satisfies the `"~> 1.0"` requirement declared in mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update castore` and commit the updated REDACTED.
Outdated: castore — `:castore` is locked at 1.0.10 but 1.0.22 is the current stable release on hex.pm, and it already satisfies the `"~> 1.0"` requirement declared in spawn_statestores/statestores/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update castore` and commit the updated REDACTED.
Outdated: cowlib — `:cowlib` is locked at 2.16.0 but 2.21.0 is the current stable release on hex.pm, and it already satisfies the `"~> 2.15"` requirement declared in mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update cowlib` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.10 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in spawn_statestores/statestores/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.17 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.7 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in spawnctl/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: do_it — `:do_it` is locked at 0.6.1 but 0.7.0 is the current stable release on hex.pm, and it already satisfies the `"~> 0.6"` requirement declared in spawnctl/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update do_it` and commit the updated REDACTED.
Outdated: ecto_psql_extras — `:ecto_psql_extras` is locked at 0.8.3 but 0.8.8 is the current stable release on hex.pm, and it already satisfies the `"~> 0.8"` requirement declared in spawn_statestores/statestores_postgres/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ecto_psql_extras` and commit the updated REDACTED.
Outdated: ecto_psql_extras — `:ecto_psql_extras` is locked at 0.8.3 but 0.8.8 is the current stable release on hex.pm, and it already satisfies the `"~> 0.7"` requirement declared in spawn_monitor/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ecto_psql_extras` and commit the updated REDACTED.
Outdated: ecto_sql — `:ecto_sql` is locked at 3.12.1 but 3.14.0 is the current stable release on hex.pm, and it already satisfies the `"~> 3.12"` requirement declared in spawn_statestores/statestores/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: ecto_sql — `:ecto_sql` is locked at 3.12.0 but 3.14.0 is the current stable release on hex.pm, and it already satisfies the `"~> 3.12"` requirement declared in spawn_statestores/statestores_postgres/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: ecto_sql — `:ecto_sql` is locked at 3.12.1 but 3.14.0 is the current stable release on hex.pm, and it already satisfies the `"~> 3.12"` requirement declared in spawn_sdk/spawn_sdk_example/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: ecto_sql — `:ecto_sql` is locked at 3.12.0 but 3.14.0 is the current stable release on hex.pm, and it already satisfies the `"~> 3.12"` requirement declared in spawn_statestores/statestores_mariadb/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: ex_doc — `:ex_doc` is locked at 0.36.1 but 0.40.4 is the current stable release on hex.pm, and it already satisfies the `">= 0.0.0"` requirement declared in spawn_statestores/statestores/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ex_doc` and commit the updated REDACTED.
Outdated: ex_doc — `:ex_doc` is locked at 0.34.2 but 0.40.4 is the current stable release on hex.pm, and it already satisfies the `">= 0.0.0"` requirement declared in spawn_statestores/statestores_native/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ex_doc` and commit the updated REDACTED.
Outdated: ex_doc — `:ex_doc` is locked at 0.36.1 but 0.40.4 is the current stable release on hex.pm, and it already satisfies the `"~> 0.25"` requirement declared in spawn_monitor/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ex_doc` and commit the updated REDACTED.
Outdated: ex_doc — `:ex_doc` is locked at 0.34.2 but 0.40.4 is the current stable release on hex.pm, and it already satisfies the `">= 0.0.0"` requirement declared in spawn_statestores/statestores_postgres/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ex_doc` and commit the updated REDACTED.
+ 29 more in this group — see findings.md.
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 01a164a6-78f9-7603-8f95-06c848878e49 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 144 · Warnings: 324 · Recommendations: 66 · Info: 54 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 17:26 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.