Public report — flux, published 4 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
127findings with an exact file:lineof 134 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
37/112dimensions across the health lenses21719 LoC — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
flipkart-incubator/flux carries serious gaps (33%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
It is strongest in Architecture (96%) — the structure is clean and changes stay contained. Domain Modelling (92%) is solid too.
The area that most needs attention is Code Health (20%) — changes there are slower and more error-prone. Accessibility (31%) is the next concern — it raises ongoing delivery and operational cost.
Leadership focus, highest impact first: TypeScript for the frontend (Type Safety); each oversized file along the responsibilities already in it (Large Files); Delete the dead files and unused exports (Dead Code).
For scale: Medium (~21,719 production lines); rebuilding it from scratch would take roughly ~0.2 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (96%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
R7 · Dead file (~12453 LoC) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js
R7 · Dead file (~324 LoC) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/codemirror/mode/xml/xml.js
R7 · Dead file (~178 LoC) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.layout.DirectedGraph.js
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.7× (at 33% quality) — the last 20% of quality is most of the work
Size & shape
Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
Dead frontend code
~12955 LoC unreachable (3 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)
This codebase represents roughly ~0.2 person-years of build effort (about ~€33,000 to rebuild). Its weakest lens is Code Health at 20% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain High (×1.4) — DDD/clean architecture, domain model × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~0.2 person-years to rebuild), and its weakest lens is Code Health at 20%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Code Health first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 7.5/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 2–5% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2/D4 code quality: averaging 7.5/10 across the code-quality signals actually measured
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
Architecture — module dependency matrix
72 modules, 144 dependencies — 2 dependency cycles, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
At a glance — Code Health · 20% · Critical · gated by R1, R3, R7
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
3
High / Critical
Roadmap
Begin by introducing TypeScript to the frontend, starting with the highest-traffic modules to establish type safety. Next, split the two largest files into smaller, focused modules to improve maintainability. Then, remove dead code and unused exports to reduce maintenance costs and rebuild times. After that, simplify branch-heavy functions to lower cyclomatic complexity. Finally, extract duplicated code blocks into shared components to eliminate redundancy.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
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. 35 of 37 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.4 — 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 — 37 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, 127 of 134 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Repo exclusion declarations: 6 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A clean result is "no unlabelled native control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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 (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 24 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 positionRelative (cyclomatic 52) finding(s) in Cyclomatic Complexity — start with joint.js. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 number (cyclomatic 48) finding(s) in Cyclomatic Complexity — start with joint.js. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 State.equals (cyclomatic 39) finding(s) in Cyclomatic Complexity — start with State.java. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 41 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 positionRelative (cognitive 73) finding(s) in Cognitive Complexity — start with joint.js. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 text (cognitive 68) finding(s) in Cognitive Complexity — start with joint.js. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 AkkaTask.onReceive (cognitive 60) finding(s) in Cognitive Complexity — start with AkkaTask.java. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.2 / 10Exemplary✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
Flux has strong documentation: a clear README with releases, changelog, why-flux, and real-time monitoring links plus an inline image of the Flux cluster dashboard; a dedicated architecture/design doc covering runtime deployment models (local/managed/isolated), detailed runtime requirements (high availability, checkpointing, fair scheduling), task/runtime separation, and a Tech Choi section. The README also references the wiki pages and CHANGELOG.md for further info, while the design doc is clipped mid-sentence and the two READMEs are thin but consistent.
The 'Why Flux' rationale mentions event sources (user actions, messages between systems, data changes to business entities) but does not explain why a state-machine-based model is preferable over an event-driven one for each of those use cases.README.md
What to do
Resolve the 1 The 'Why Flux' rationale mentions event sources (user actions, messages… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
High: object-deserialization · ×2persistence-mysql/src/main/java/com/flipkart/flux/type/BlobType.java:109detected by semgrep finding
Medium: weak-randomexamples/src/main/java/com/flipkart/flux/examples/decision/UserVerificationService.java:28detected by semgrep finding
What to do
Resolve the 2 High finding(s) in Static Analysis (SAST) — start with BlobType.java (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Medium finding(s) in Static Analysis (SAST) — start with UserVerificationService.java. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d29_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.
108 of 108 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java.
Largest orphaned file · ×3runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java
Dormant codebase
What to do
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with StateMachineResource.java, WorkFlowExecutionController.java, AkkaTask.java. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — hystrixCircuitContainer.html:16
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Do you agree with this assessment?
AC3 · Page structure4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — monitor.html:2
An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — monitor.html:33
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. (×9) — monitor.html:44, monitor.html:45, monitor.html:46, …
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
`hr` sets color: #007C00 on background-color: #007C00 — 1.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — local.css:60
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline.
What to do
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Do you agree with this assessment?
DM4 · Rich vs anemic model8.2 / 10Strong✓ Tool-verified
Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`ScheduledEvent` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — ScheduledEvent.java:30
`ScheduledMessage` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — ScheduledMessage.java:30
What to do
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
Other · Domain Modelling — Whether entities protect their state (private/init-only setters) instead of exposing public setters that bypass invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): public setters on entities detected; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 10 of 10 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents 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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
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.
Do you agree with this assessment?
P1 · CI/CD gates7.0 / 10Strong✓ Tool-verified
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.
A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
What to do
Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
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 spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step.
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 6 plain JS — the untyped files are runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/codemirror/mode/xml/xml.js, runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js, runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixThreadPool/hystrixThreadPool.js, runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js, runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.layout.DirectedGraph.js, runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/tmpl.js.
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm over JS/TS tokens, D-386).
Method: Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm run over JS/TS tokens). Deterministic.
runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:9313 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:9340 — all 2 copies are in the same file, and what repeats is a LIST OF ENTRIES rather than behaviour — the same names written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — joint.js:9313
runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:9258 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:9289 — all 2 copies are in the same file, and what repeats is a LIST OF ENTRIES rather than behaviour — the same names written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — joint.js:9258
runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:12364 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.layout.DirectedGraph.js:97 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — joint.js:12364
runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:70 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixThreadPool/hystrixThreadPool.js:65 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — hystrixCommand.js:70
runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:512 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixThreadPool/hystrixThreadPool.js:315 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — hystrixCommand.js:512
runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:287 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixThreadPool/hystrixThreadPool.js:226 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — hystrixCommand.js:287
runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:368 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:381 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:395 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:408 — 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. — hystrixCommand.js:368
runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:418 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:436 · runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:454 — 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. — hystrixCommand.js:418
What to do
Extract the duplicated blocks into shared functions/components.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×8) — joint.js:5900, joint.js:3184, joint.js:1209, …
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
2 file(s) over 400 lines (counted as significant lines — blank lines excluded — over production source only, tests excluded), largest first: runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js (9386), runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js (461).
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
0% of 6 production file(s) reachable from 0 test file(s) via the import graph
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R7 · Dead Code0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 3 application, 0 tooling and 0 test entry point(s) detected in this repo. Gate removals on your build/type-check — an undetected custom entry would make these reachable.
no import path from any entry point (3 application, 0 tooling, 0 test roots considered) (×3) — joint.js, xml.js, joint.layout.DirectedGraph.js
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 75 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.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over a document set 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
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph 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 — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) 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
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.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~7273 lines of test source are present (.java) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (a Maven POM), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.java) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the 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
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Maven POM — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
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.
D38 OSV Dependency Vulnerabilities — Scanner failed to run — not a clean result
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .java, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
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 (.java) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check 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 check looks for
GD1 Unfinished & placeholder code — no source files
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, 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'.
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D33 (JS/npm Dependency Vulnerabilities)
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not 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
X3 Exception handling — 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
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 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
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: StatesDAOImpl.java ↔ ReplayEventPersistenceService.java persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOImpl.java— `persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOImpl.java` (context persistence-mysql) and `runtime/src/main/java/com/flipkart/flux/representation/ReplayEventPersistenceService.java` (context runtime) sit in DIFFERENT parts of the tree yet change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — 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.
Boundary-crossing change coupling: WorkFlowExecutionController.java ↔ RedriverRegistryImpl.java runtime/src/main/java/com/flipkart/flux/controller/WorkFlowExecutionController.java— `runtime/src/main/java/com/flipkart/flux/controller/WorkFlowExecutionController.java` (context runtime) and `task/src/main/java/com/flipkart/flux/impl/redriver/RedriverRegistryImpl.java` (context task) sit in DIFFERENT parts of the tree yet change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — 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.
Boundary-crossing change coupling: EventsDAOImpl.java ↔ WorkFlowExecutionController.java persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/EventsDAOImpl.java— `persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/EventsDAOImpl.java` (context persistence-mysql) and `runtime/src/main/java/com/flipkart/flux/controller/WorkFlowExecutionController.java` (context runtime) sit in DIFFERENT parts of the tree yet change together 51% of the time (29 of the 57 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — 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.
Boundary-crossing change coupling: WorkFlowExecutionController.java ↔ FluxError.java runtime/src/main/java/com/flipkart/flux/controller/WorkFlowExecutionController.java— `runtime/src/main/java/com/flipkart/flux/controller/WorkFlowExecutionController.java` (context runtime) and `task/src/main/java/com/flipkart/flux/api/core/FluxError.java` (context task) sit in DIFFERENT parts of the tree yet change together 50% of the time (10 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — 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.
Boundary-crossing change coupling: TransactionInterceptor.java ↔ ParallelScatterGatherQueryHelper.java common/src/main/java/com/flipkart/flux/guice/interceptor/TransactionInterceptor.java— `common/src/main/java/com/flipkart/flux/guice/interceptor/TransactionInterceptor.java` (context common) and `persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/ParallelScatterGatherQueryHelper.java` (context persistence-mysql) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — 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.
Boundary-crossing change coupling: StateMachineResource.java ↔ RedriverRegistryImpl.java runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java— `runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java` (context runtime) and `task/src/main/java/com/flipkart/flux/impl/redriver/RedriverRegistryImpl.java` (context task) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — 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.
High: object-deserialization persistence-mysql/src/main/java/com/flipkart/flux/type/BlobType.java:109— Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data stream to make sure it is not tampered with, or consider only transmitting object fields and populating a new object. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
High: object-deserialization persistence-mysql/src/main/java/com/flipkart/flux/type/BlobType.java:173— Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data stream to make sure it is not tampered with, or consider only transmitting object fields and populating a new object. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Duplicated block (8 lines × 2) client/src/main/java/com/flipkart/flux/client/runtime/FluxRuntimeConnectorHttpImpl.java:130— client/src/main/java/com/flipkart/flux/client/runtime/FluxRuntimeConnectorHttpImpl.java:130-137 | client/src/main/java/com/flipkart/flux/client/runtime/FluxRuntimeConnectorHttpImpl.java:188-195 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `client/src/main/java/com/flipkart/flux/client/runtime/FluxRuntimeConnectorHttpImpl.java:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) common/src/main/java/com/flipkart/flux/guice/interceptor/TransactionInterceptor.java:91— common/src/main/java/com/flipkart/flux/guice/interceptor/TransactionInterceptor.java:91-98 | common/src/main/java/com/flipkart/flux/guice/interceptor/TransactionInterceptor.java:109-116 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/java/com/flipkart/flux/guice/interceptor/TransactionInterceptor.java:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) runtime/src/main/java/com/flipkart/flux/guice/module/ShardModule.java:243— runtime/src/main/java/com/flipkart/flux/guice/module/ShardModule.java:243-250 | runtime/src/main/java/com/flipkart/flux/guice/module/ShardModule.java:265-273 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `runtime/src/main/java/com/flipkart/flux/guice/module/ShardModule.java:243` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) runtime/src/main/java/com/flipkart/flux/guice/module/ShardModule.java:313— runtime/src/main/java/com/flipkart/flux/guice/module/ShardModule.java:313-320 | scheduler/src/main/java/com/flipkart/flux/module/SchedulerModule.java:77-84 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) persistence/src/main/java/com/flipkart/flux/persistence/EntityManager.java:66— persistence/src/main/java/com/flipkart/flux/persistence/EntityManager.java:66-73 | persistence/src/main/java/com/flipkart/flux/persistence/MultiEntityManager.java:131-138 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/src/main/java/com/flipkart/flux/persistence/EntityManager.java:66` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:164— persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:164-171 | runtime/src/main/java/com/flipkart/flux/representation/StateMachinePersistenceService.java:111-118 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:164` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:204— persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:204-211 | runtime/src/main/java/com/flipkart/flux/representation/StateMachinePersistenceService.java:242-249 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:204` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:215— persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:215-222 | runtime/src/main/java/com/flipkart/flux/representation/EventPersistenceService.java:46-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:215` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) runtime/src/main/java/com/flipkart/flux/resource/ClientElbResource.java:87— runtime/src/main/java/com/flipkart/flux/resource/ClientElbResource.java:87-94 | runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:214-221 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `runtime/src/main/java/com/flipkart/flux/resource/ClientElbResource.java:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) api/src/main/java/com/flipkart/flux/api/ExecutionUpdateData.java:61— api/src/main/java/com/flipkart/flux/api/ExecutionUpdateData.java:61-70 | task/src/main/java/com/flipkart/flux/impl/message/TaskAndEvents.java:91-100 — 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. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
Duplicated block (10 lines × 2) runtime/src/main/java/com/flipkart/flux/guice/module/ExecutionContainerModule.java:82— runtime/src/main/java/com/flipkart/flux/guice/module/ExecutionContainerModule.java:82-91 | runtime/src/main/java/com/flipkart/flux/guice/module/OrchestratorContainerModule.java:85-94 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `runtime/src/main/java/com/flipkart/flux/guice/module/ExecutionContainerModule.java:82` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) runtime/src/main/java/com/flipkart/flux/guice/module/ExecutionContainerModule.java:98— runtime/src/main/java/com/flipkart/flux/guice/module/ExecutionContainerModule.java:98-107 | runtime/src/main/java/com/flipkart/flux/guice/module/OrchestratorContainerModule.java:102-113 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) runtime/src/main/java/com/flipkart/flux/controller/WorkFlowExecutionController.java:154— runtime/src/main/java/com/flipkart/flux/controller/WorkFlowExecutionController.java:154-163 | runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:158-167 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:335— runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:335-345 | runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:454-463 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:335` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:638— runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:638-647 | runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:744-753 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:638` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StateTraversalPathDAOV1Impl.java:82— persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StateTraversalPathDAOV1Impl.java:82-86 | persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:215-219 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (5 lines × 2) persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:145— persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:145-149 | persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:158-162 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:145` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:152— persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:152-156 | runtime/src/main/java/com/flipkart/flux/representation/StateMachinePersistenceService.java:99-103 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:152` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java:137— task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java:137-141 | task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java:217-221 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java:137` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java:180— task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java:180-185 | task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java:201-205 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java:180` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) task/src/main/java/com/flipkart/flux/impl/task/HookExecutor.java:47— task/src/main/java/com/flipkart/flux/impl/task/HookExecutor.java:47-51 | task/src/main/java/com/flipkart/flux/impl/task/TaskExecutor.java:71-75 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `task/src/main/java/com/flipkart/flux/impl/task/HookExecutor.java:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Change coupling: StatesDAOImpl.java ↔ StateMachinesDAO.java persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOImpl.java— `persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOImpl.java` and `persistence/src/main/java/com/flipkart/flux/persistence/dao/iface/StateMachinesDAO.java` change together 66% of the time (19 of the 29 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) 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.
Change coupling: StateMachinesDAO.java ↔ StatesDAO.java persistence/src/main/java/com/flipkart/flux/persistence/dao/iface/StateMachinesDAO.java— `persistence/src/main/java/com/flipkart/flux/persistence/dao/iface/StateMachinesDAO.java` and `persistence/src/main/java/com/flipkart/flux/persistence/dao/iface/StatesDAO.java` change together 62% of the time (18 of the 29 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
Change coupling: TaskExecutor.java ↔ TaskRegistry.java task/src/main/java/com/flipkart/flux/impl/task/TaskExecutor.java— `task/src/main/java/com/flipkart/flux/impl/task/TaskExecutor.java` and `task/src/main/java/com/flipkart/flux/impl/task/TaskRegistry.java` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
Change coupling: LocalJvmTask.java ↔ TaskExecutor.java task/src/main/java/com/flipkart/flux/impl/task/LocalJvmTask.java— `task/src/main/java/com/flipkart/flux/impl/task/LocalJvmTask.java` and `task/src/main/java/com/flipkart/flux/impl/task/TaskExecutor.java` change together 57% of the time (13 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
FileTooLong: js/joint.js runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:0— FileTooLong — 6226 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). 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: resource/StateMachineResource.java runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:0— FileTooLong — 846 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: StateMachineResource (106-1247). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
TooManyMethods: State model/src/main/java/com/flipkart/flux/domain/State.java:38— TooManyMethods — 47 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StateDefinition api/src/main/java/com/flipkart/flux/api/StateDefinition.java:30— TooManyMethods — 31 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (11 lines × 2) api/src/main/java/com/flipkart/flux/api/StateDefinition.java:123— api/src/main/java/com/flipkart/flux/api/StateDefinition.java:123-133 | model/src/main/java/com/flipkart/flux/domain/State.java:182-192 — 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 (11 lines × 2) persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:232— persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:232-242 | runtime/src/main/java/com/flipkart/flux/representation/StateMachinePersistenceService.java:258-268 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:232` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/AuditDAOImpl.java:56— persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/AuditDAOImpl.java:56-64 | persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/AuditDAOV1Impl.java:46-54 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:248— persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:248-256 | runtime/src/main/java/com/flipkart/flux/representation/StateMachinePersistenceService.java:274-282 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:90— persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:90-96 | runtime/src/main/java/com/flipkart/flux/representation/StateMachinePersistenceService.java:149-155 — 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) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:612— runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:612-619 | runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:720-726 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:612` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
positionRelative (cyclomatic 52) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:5900— positionRelative has cyclomatic complexity 52 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity· number (cyclomatic 48) · ×1
number (cyclomatic 48) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:3184— number has cyclomatic complexity 48 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
State.equals (cyclomatic 39) model/src/main/java/com/flipkart/flux/domain/State.java:370— State.equals has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity· text (cyclomatic 29) · ×1
text (cyclomatic 29) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:1209— text has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
fitToContent (cyclomatic 27) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:8387— fitToContent has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
StateDefinition.equals (cyclomatic 25) api/src/main/java/com/flipkart/flux/api/StateDefinition.java:238— StateDefinition.equals has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StateMachine.equals (cyclomatic 23) model/src/main/java/com/flipkart/flux/domain/StateMachine.java:203— StateMachine.equals has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
onEndModelChange (cyclomatic 22) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:7314— onEndModelChange has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
pointermove (cyclomatic 22) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:7930— pointermove has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
AkkaTask.onReceive (cyclomatic 21) task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java:105— AkkaTask.onReceive has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
breakText (cyclomatic 21) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:2587— breakText has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
getConnectionPoint (cyclomatic 21) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:7598— getConnectionPoint has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
State.hashCode (cyclomatic 20) model/src/main/java/com/flipkart/flux/domain/State.java:405— State.hashCode has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StateMachineResource.submitEvent (cyclomatic 20) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:282— StateMachineResource.submitEvent has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parseTransformString (cyclomatic 19) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:999— parseTransformString has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
annotateString (cyclomatic 19) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:2082— annotateString has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
sortSameAsLast (cyclomatic 19) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:471— sortSameAsLast has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
StateMachineResource.submitReplayEvent (cyclomatic 18) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:402— StateMachineResource.submitReplayEvent has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
(anonymous) (cyclomatic 18) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:5770— (anonymous) has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
findRoute (cyclomatic 18) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:10271— findRoute has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
inText (cyclomatic 18) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/codemirror/mode/xml/xml.js:47— inText has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
StateMachineResource.updateEvent (cyclomatic 17) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:605— StateMachineResource.updateEvent has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StateMachineResource.updateInternalEvent (cyclomatic 17) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:714— StateMachineResource.updateInternalEvent has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
(anonymous) (cyclomatic 17) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:3937— (anonymous) has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
pointerdown (cyclomatic 17) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:7849— pointerdown has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
findOrthogonalRoute (cyclomatic 17) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:9891— findOrthogonalRoute has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
sortSameAsLast (cyclomatic 17) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixThreadPool/hystrixThreadPool.js:278— sortSameAsLast has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
TransactionInterceptor.invoke (cyclomatic 16) common/src/main/java/com/flipkart/flux/guice/interceptor/TransactionInterceptor.java:66— TransactionInterceptor.invoke has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Event.equals (cyclomatic 16) model/src/main/java/com/flipkart/flux/domain/Event.java:188— Event.equals has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
dormant codebase — no living knowledge left to concentrate — All 92 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
positionRelative (cognitive 73) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:5900— positionRelative has cognitive complexity 73 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity· text (cognitive 68) · ×1
text (cognitive 68) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:1209— text has cognitive complexity 68 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AkkaTask.onReceive (cognitive 60) task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java:105— AkkaTask.onReceive has cognitive complexity 60 (threshold 15). Drivers by points: if/else 38, error handling 14, loops 5, boolean chains 3 (nesting depth added 34). 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.
State.equals (cognitive 55) model/src/main/java/com/flipkart/flux/domain/State.java:370— State.equals has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 34, if/else 21 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransactionInterceptor.invoke (cognitive 42) common/src/main/java/com/flipkart/flux/guice/interceptor/TransactionInterceptor.java:66— TransactionInterceptor.invoke has cognitive complexity 42 (threshold 15). Drivers by points: if/else 29, error handling 8, match/switch 5 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
breakText (cognitive 42) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:2587— breakText has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity· number (cognitive 41) · ×1
number (cognitive 41) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:3184— number has cognitive complexity 41 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
findRoute (cognitive 40) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:10271— findRoute has cognitive complexity 40 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StateMachineResource.submitEvent (cognitive 36) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:282— StateMachineResource.submitEvent has cognitive complexity 36 (threshold 15). Drivers by points: if/else 22, error handling 10, boolean chains 4 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
inText (cognitive 36) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/codemirror/mode/xml/xml.js:47— inText has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pointermove (cognitive 34) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:7930— pointermove has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StateDefinition.equals (cognitive 33) api/src/main/java/com/flipkart/flux/api/StateDefinition.java:238— StateDefinition.equals has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 19, if/else 13, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
annotateString (cognitive 33) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:2082— annotateString has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StateMachine.equals (cognitive 32) model/src/main/java/com/flipkart/flux/domain/StateMachine.java:203— StateMachine.equals has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 20, if/else 12 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
findOrthogonalRoute (cognitive 30) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:9891— findOrthogonalRoute has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
onEndModelChange (cognitive 29) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:7314— onEndModelChange has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getConnectionPoint (cognitive 29) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:7598— getConnectionPoint has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkFlowExecutionController.cancelPath (cognitive 28) runtime/src/main/java/com/flipkart/flux/controller/WorkFlowExecutionController.java:247— WorkFlowExecutionController.cancelPath has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16, loops 6, error handling 5, boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fitToContent (cognitive 27) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:8387— fitToContent has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClientElbResource.createClientElb (cognitive 24) runtime/src/main/java/com/flipkart/flux/resource/ClientElbResource.java:58— ClientElbResource.createClientElb has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11, error handling 8, ternaries 3, boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StateMachineExecutionEntitiesManager.validateReplayableStates (cognitive 23) persistence/src/main/java/com/flipkart/flux/persistence/StateMachineExecutionEntitiesManager.java:150— StateMachineExecutionEntitiesManager.validateReplayableStates has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16, loops 4, boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StateMachinePersistenceService.validateReplayableStates (cognitive 23) runtime/src/main/java/com/flipkart/flux/representation/StateMachinePersistenceService.java:96— StateMachinePersistenceService.validateReplayableStates has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16, loops 4, boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StateMachineResource.submitReplayEvent (cognitive 23) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:402— StateMachineResource.submitReplayEvent has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13, error handling 8, boolean chains 2 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
pointerdown (cognitive 23) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:7849— pointerdown has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StateMachineResource.updateEvent (cognitive 22) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:605— StateMachineResource.updateEvent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12, boolean chains 4, error handling 4, loops 2 (nesting depth added 6). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
pointerup (cognitive 22) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:8102— pointerup has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Event.equals (cognitive 21) model/src/main/java/com/flipkart/flux/domain/Event.java:188— Event.equals has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 12, if/else 9 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeploymentUnitsManagerImpl.initialize (cognitive 21) runtime/src/main/java/com/flipkart/flux/deploymentunit/DeploymentUnitsManagerImpl.java:153— DeploymentUnitsManagerImpl.initialize has cognitive complexity 21 (threshold 15). Drivers by points: error handling 12, if/else 4, loops 4, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parseTransformString (cognitive 21) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:999— parseTransformString has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
State.hashCode (cognitive 19) model/src/main/java/com/flipkart/flux/domain/State.java:405— State.hashCode has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 19. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StateMachineResource.createStateMachine (cognitive 19) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:183— StateMachineResource.createStateMachine has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9, ternaries 6, error handling 3, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 18) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:7156— (anonymous) has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
router (cognitive 18) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:10401— router has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sortSameAsLast (cognitive 18) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixCommand/hystrixCommand.js:471— sortSameAsLast has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VersionedEventData.equals (cognitive 17) api/src/main/java/com/flipkart/flux/api/VersionedEventData.java:143— VersionedEventData.equals has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 9, if/else 7, boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkFlowExecutionController.executeStates (cognitive 17) runtime/src/main/java/com/flipkart/flux/controller/WorkFlowExecutionController.java:644— WorkFlowExecutionController.executeStates has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, boolean chains 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StateMachineResource.updateInternalEvent (cognitive 17) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:714— StateMachineResource.updateInternalEvent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, boolean chains 3, error handling 1, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
containsRect (cognitive 17) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:466— containsRect has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createElement (cognitive 17) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:924— createElement has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
flattenObject (cognitive 17) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:2332— flattenObject has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
linkAllowed (cognitive 17) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:8921— linkAllowed has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeploymentUnit.populateTaskMethods (cognitive 16) runtime/src/main/java/com/flipkart/flux/deploymentunit/DeploymentUnit.java:207— DeploymentUnit.populateTaskMethods has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, loops 7, error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RedriverService.redrive (cognitive 16) scheduler/src/main/java/com/flipkart/flux/redriver/service/RedriverService.java:116— RedriverService.redrive has cognitive complexity 16 (threshold 15). Drivers by points: loops 6, if/else 5, error handling 4, boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 16) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:3937— (anonymous) has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
processEmbedding (cognitive 16) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/js/joint.js:6247— processEmbedding has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sortSameAsLast (cognitive 16) runtime/src/main/resources/packaged/webapps/dashboard/WEB-INF/pages/resources/components/hystrixThreadPool/hystrixThreadPool.js:278— sortSameAsLast has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Medium: weak-random examples/src/main/java/com/flipkart/flux/examples/decision/UserVerificationService.java:28— Detected use of the functions `Math.random()` or `java.util.Random()`. These are both not cryptographically strong random number generators (RNGs). If you are using these RNGs to create passwords or secret tokens, use `java.security.SecureRandom` instead. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
Duplicated block (8 lines × 3) runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:300— runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:300-307 | runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:633-641 | runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:739-747 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java:300` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:162— persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:162-167 | persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:182-187 | persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:195-200 — 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 (6 lines × 2) persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/EventsDAOImpl.java:254— persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/EventsDAOImpl.java:254-260 | persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/EventsDAOImpl.java:342-347 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/EventsDAOImpl.java:254` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 3) persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:133— persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:133-137 | persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:212-216 | persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:242-246 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `persistence-mysql/src/main/java/com/flipkart/flux/persistence/dao/impl/StatesDAOV1Impl.java:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Recommendation — 8 finding(s)
D34 · Knowledge Freshness· Largest orphaned file · ×3
Largest orphaned file runtime/src/main/java/com/flipkart/flux/resource/StateMachineResource.java— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file runtime/src/main/java/com/flipkart/flux/controller/WorkFlowExecutionController.java— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file task/src/main/java/com/flipkart/flux/impl/task/AkkaTask.java— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.java) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D19 · Documentation Quality· The 'Why Flux' rationale mentions event sources (user actions, messages between systems, data changes to business entities) but does not explain why a state-machine-based model is preferable over an event-driven one for each of those use cases. · ×1
The 'Why Flux' rationale mentions event sources (user actions, messages between systems, data changes to business entities) but does not explain why a state-machine-based model is preferable over an event-driven one for each of those use cases. README.md— Expand on the tradeoffs: why a state machine rather than an event stream for each source type. For example, when concurrency and fault tolerance are more important than latency.
Dormant codebase — 108 of 108 significant files have no living knowledge — the codebase as a whole is dormant, not 108 separate risks. Re-engage owners or document before change.
D38 · OSV Dependency Vulnerabilities· Scanner failed to run · ×1
Scanner failed to run — not a clean result — osv-scanner exited 128 with no findings — the advisory database was likely unreachable. The scanner exited non-zero and produced no findings (typically the advisory DB was unreachable), so this is reported as a measurement gap rather than a clean pass.
Coverage not included — suite not readable by the collector — Coverage NOT MEASURED: test source is present (.java) 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 (JaCoCo XML — `mvn jacoco:report`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored.
Info — 2 finding(s)
D12 · Dependency Hygiene· Dependency hygiene not measured · ×1
Dependency hygiene not measured — dependency manifest found but not parsed for hygiene — This repository's dependency manifest (a Maven POM) was found, but this pass cannot parse it for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D38 wherever the manifest is OSV-readable.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
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.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
0
—
Run 019fcec2-9284-7cc8-a2db-7621ddca9b65 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 8 · Warnings: 116 · Recommendations: 8 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 04-08-2026 @ 21:51 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.