SimTong-Android — Watchdog Audit

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.

Team-ComIT/SimTong-Android is sound in substance but carries real gaps (58%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.

It is strongest in Code Health (95%) — the code is clean and low-risk to change. Architecture (82%) is solid too.

The area that most needs attention is Maturity (45%) — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent. Readiness (57%) is the next concern — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade.

Leadership focus, highest impact first: Record significant decisions one document per decision (Architecture documentation); Expand the README with getting-started (Documentation (README)); 1 Dormant codebase finding(s) in Knowledge Freshness (Knowledge Freshness).

For scale: Small (~18,168 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.

Encouragingly, the gaps are in documentation and release process — not in the code's correctness, structure or security, which are strong. They're low-risk to close, and doing so would lift the grade without re-engineering anything that already works.

Code Health 95% ★ Exemplary Architecture 82% Strong Maturity 45% Weak · gated by D34, M2 Readiness 57% Adequate · gated by P3 Security 79% Strong

How the score is built — each lens's share of the headline Width 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.

Maturity 45% · 47% weightReadiness 57% · 26% weightSecurity 79% · 14% weightArchitecture 82% · 8% weightCode Health 95% · 4% weight

Raise Maturity 45 → 70 (the Healthy floor) ⇒ headline 58 → ~67.

Code composition — where the lines go

Tests 100%

New since the last scan (14+)

14 finding(s) are new versus the previous scan (2026-07-29) — surfaced by this scheduled scan itself, no pull request required.

D4 · Duplicated block (19 lines × 2) common-compose/src/main/java/com/comit/common/BtnField.kt
D4 · Duplicated block (19 lines × 2) core-design-system/src/main/java/com/comit/core_design_system/component/Vote.kt
D4 · Duplicated block (17 lines × 2) common-compose/src/main/java/com/comit/common/BtnField.kt
D4 · Duplicated block (16 lines × 3) feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/1_SignUpNameScreen.kt
D4 · Duplicated block (16 lines × 2) core-design-system/src/main/java/com/comit/core_design_system/typography/typography.kt
D4 · Duplicated block (15 lines × 2) feature/feature-home/src/main/java/com/comit/feature_home/screen/WriteClosedDayScreen.kt
D4 · Duplicated block (14 lines × 2) feature/feature-home/src/main/java/com/comit/feature_home/screen/schedule/ShowScheduleScreen.kt
D4 · Duplicated block (11 lines × 2) common-compose/src/main/java/com/comit/common/SimImageUploadLayout.kt
D4 · Duplicated block (10 lines × 2) common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt
D4 · Duplicated block (9 lines × 2) common-util/src/main/java/com/comit/common/unit/bitmap.kt
D4 · Duplicated block (8 lines × 2) common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt
D4 · Duplicated block (6 lines × 2) common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt
D35 · Change coupling clique: AuthFindScreen.kt, FindPasswordEmailCodeScreen.kt, FindPasswordFixPasswordScreen.kt feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/find/AuthFindScreen.kt
D35 · Change coupling: 3_SignUpPasswordScreen.kt ↔ 4_SignUpNicknameScreen.kt feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/3_SignUpPasswordScreen.kt

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.

Rebuild cost & value ~ Modeled — €6,300–€32,000

Cost to rebuild	€6,300–€32,000 (0.1–0.2 person-years (105–334 h), ~1 engineer)
Domain complexity	Standard — harder problems cost more per line
Quality factor	0.8× (at 58% quality) — the last 20% of quality is most of the work
Size & shape	Small · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~0.1 person-years of build effort (about ~€19,000 to rebuild). Its weakest lens is Maturity at 45% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.8× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness.

+12.9 pts · Low effort · Knowledge Freshness

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).

+13.2 pts · Medium effort · Architecture documentation

Expand the README with getting-started, architecture overview and a project map.

+13.1 pts · Medium effort · Documentation (README)

Diagnosis — what's actually going on

Value concentrated against a weak lens · High · Value at risk

This is a Small asset (~0.1 person-years to rebuild), and its weakest lens is Maturity at 45%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Small, ~0.1 person-years rebuild (18,168 LoC) · weakest lens: Maturity 45%

→ Direct remediation budget at Maturity 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: 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). The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ 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).

Architecture — module dependency matrix

162 modules, 134 dependencies — every dependency points down the layering, so there are no cycles. 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 · 95% · Exemplary

The Good

D1 · Kotlin Cyclomatic Complexity 9.4 D2 · Kotlin Cognitive Complexity 9.1 D3 · Kotlin God Classes 9.8 D4 · Kotlin Code Duplication 9.7

At a glance — Architecture · 82% · Strong

The Good

D35 · Kotlin Change Coupling 8.2

At a glance — Maturity · 45% · Weak · gated by D34, M2

The Good

D15 · Kotlin Churn × Complexity Hotspots 10.0 D21 · Kotlin Naming Consistency 10.0 M3 · Repo Folder & project structure 10.0

The Bad

M4 · Repo Documentation accuracy 5.0

The Ugly

D19 · Kotlin Documentation Quality 4.0 D34 · Kotlin Knowledge Freshness 0.0 M1 · Repo Documentation (README) 4.7 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 57% · Adequate · gated by P3

The Good

D13 · Kotlin Secret Scanning 10.0 P1 · Repo CI/CD gates 10.0

The Ugly

P3 · Repo Security & performance tooling 0.0

At a glance — Security · 79% · Strong

The Good

D28 · Kotlin Secrets (history) 10.0 D29 · Kotlin Static Analysis (SAST) 7.1

The Bad

D38 · Kotlin OSV Dependency Vulnerabilities 6.5

Security & Compliance — OWASP Top-10 mapping

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
A06:2021 — Vulnerable & Outdated Components	7	High / Critical
A03:2021 — Injection	2	High / Critical

Roadmap

Begin by documenting significant architectural decisions in a dedicated folder to capture context and consequences. Expand the root README to include a project map, architecture overview, and getting-started guide. Ensure the documentation accurately reflects the current state of the codebase, correcting any discrepancies between the README and the actual project structure. Finally, address dormant codebase findings to maintain knowledge freshness and improve overall documentation quality.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness.	+12.9 pts	Low	Knowledge Freshness
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).	+13.2 pts	Medium	Architecture documentation
Expand the README with getting-started, architecture overview and a project map.	+13.1 pts	Medium	Documentation (README)
Reconcile the README with reality: README claims 'MVP service' while the evidence shows a complete project tree (292 source files).	+12.9 pts	Medium	Documentation accuracy
Improve Documentation Quality — currently 4.0/10.	+10.4 pts	Medium	Documentation Quality
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.	+7.4 pts	Medium	Security & performance tooling
Resolve the 3 Boundary-crossing change coupling finding(s) in Change Coupling — start with GetHolidayViewModel.kt, SimTongCalendar.kt, SimTongCalendarDialog.kt.	+1.2 pts	Low	Change Coupling
Resolve the 2 High finding(s) in Static Analysis (SAST) — start with ci.yml (2).	+1.0 pts	Low	Static Analysis (SAST)

File quality

Per-file score 0–10 — a quality signature. Of 19 files carrying findings, judged against the Production bar: 5% slop · 48% mixed · 47% near-clean.

File	Score	Band	Worst signal
Gemfile.lock	1.4	Slop	OSV Dependency Vulnerabilities: High CVE: [GHSA redacted]
common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt	5.4	Mixed	Change Coupling: Boundary-crossing change coupling: SimTongCalendarDialog.kt ↔ WriteScheduleScreen.kt
.github/workflows/ci.yml	5.8	Mixed	Static Analysis (SAST): High: github-actions-mutable-action-tag
feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendarGetList.kt	6.3	Mixed	Cyclomatic Complexity: SimTongCalendarGetListKt.organizeList (cyclomatic 19)
feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendar.kt	6.5	Mixed	Change Coupling: Boundary-crossing change coupling: SimTongCalendar.kt ↔ HolidayAPI.kt
feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/1_SignUpNameScreen.kt	7.0	Mixed	Code Duplication: Duplicated block (16 lines × 3)
feature/feature-home/src/main/java/com/comit/feature_home/screen/WriteClosedDayScreen.kt	7.0	Mixed	Code Duplication: Duplicated block (15 lines × 2)
core-design-system/src/main/java/com/comit/core_design_system/typography/typography.kt	7.8	Mixed	God Classes: FileTooLong: typography/typography.kt
common-compose/src/main/java/com/comit/common/BtnField.kt	7.8	Mixed	Code Duplication: Duplicated block (19 lines × 2)
feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/2_SignUpVerifyScreen.kt	7.8	Mixed	Change Coupling: Change coupling: 2_SignUpVerifyScreen.kt ↔ 3_SignUpPasswordScreen.kt
feature/feature-home/src/main/java/com/comit/feature_home/vm/GetHolidayViewModel.kt	8.0	Near-clean	Change Coupling: Boundary-crossing change coupling: GetHolidayViewModel.kt ↔ RemoteHolidayDataSourceImpl.kt
feature/feature-mypage/src/main/java/com/comit/feature_mypage/screen/fix/password/FixPassword.kt	8.5	Near-clean	Cyclomatic Complexity: FixPasswordKt.FixPassword (cyclomatic 21)
data/src/main/java/com/comit/data/util/SimTongApiCall.kt	8.5	Near-clean	Cyclomatic Complexity: SimTongApiCallKt.simTongApiCall (cyclomatic 19)
core-design-system/src/main/java/com/comit/core_design_system/component/Vote.kt	8.5	Near-clean	Code Duplication: Duplicated block (19 lines × 2)
feature/feature-home/src/main/java/com/comit/feature_home/screen/schedule/ShowScheduleScreen.kt	8.5	Near-clean	Code Duplication: Duplicated block (14 lines × 2)
common-compose/src/main/java/com/comit/common/SimImageUploadLayout.kt	8.5	Near-clean	Code Duplication: Duplicated block (11 lines × 2)
common-util/src/main/java/com/comit/common/unit/bitmap.kt	8.5	Near-clean	Code Duplication: Duplicated block (9 lines × 2)
feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/find/AuthFindScreen.kt	8.5	Near-clean	Change Coupling: Change coupling clique: AuthFindScreen.kt, FindPasswordEmailCodeScreen.kt, FindPasswordFixPasswordScreen.kt
feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/3_SignUpPasswordScreen.kt	8.5	Near-clean	Change Coupling: Change coupling: 3_SignUpPasswordScreen.kt ↔ 4_SignUpNicknameScreen.kt

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 17 of 19 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 — 19 dimensions across the health lenses

D1D2D3D4D13D15D19D21D28D29D34D35D38M1M2M3M4P1P3

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, 37 of 43 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
jscpd	Code duplication	—	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.302	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.302	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 019fc9ff-f22f-785f-87d6-dfe9e6fee2d1.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
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.
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.

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.

Dimensions

D1 · Cyclomatic Complexity9.4 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Prevented

3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FixPasswordKt.FixPassword at 21. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SignUpScreenKt.SignUpScreen at 18 — they are counted neither in the figure above nor in this dimension's score.

FixPasswordKt.FixPassword (cyclomatic 21)feature/feature-mypage/src/main/java/com/comit/feature_mypage/screen/fix/password/FixPassword.kt:68

SimTongApiCallKt.simTongApiCall (cyclomatic 19)data/src/main/java/com/comit/data/util/SimTongApiCall.kt:39

SimTongCalendarGetListKt.organizeList (cyclomatic 19)feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendarGetList.kt:26

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D2 · Cognitive Complexity9.1 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.1 / 10 · rule-coverage 100% · ceiling Prevented

2 method(s) exceeded the cognitive complexity threshold of 15; the worst was SimTongCalendarGetListKt.organizeList at 31.

SimTongCalendarGetListKt.organizeList (cognitive 31)feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendarGetList.kt:26

SimTongCalendarKt.SimTongCalendarItem (cognitive 17)feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendar.kt:368

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D3 · God Classes9.8 / 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.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Prevented

1 god class(es) detected.

FileTooLong: typography/typography.ktcore-design-system/src/main/java/com/comit/core_design_system/typography/typography.kt:0

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D4 · Code Duplication9.7 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Verified

12 duplicated block group(s) detected.

Duplicated block (19 lines × 2) · ×2common-compose/src/main/java/com/comit/common/BtnField.kt:104

Duplicated block (17 lines × 2)common-compose/src/main/java/com/comit/common/BtnField.kt:74

Duplicated block (16 lines × 3)feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/1_SignUpNameScreen.kt:311

Duplicated block (16 lines × 2)core-design-system/src/main/java/com/comit/core_design_system/typography/typography.kt:456

Duplicated block (15 lines × 2)feature/feature-home/src/main/java/com/comit/feature_home/screen/WriteClosedDayScreen.kt:259

+ 6 more group(s) — more in Appendix A; the complete list is findings.md.

✓ On the Gold path — maintain.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D19 · Documentation Quality / 10Weak◐ Sampled · advisory

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.

Maturity: Documented → Verified → Prevented · effective Weak / 10 · rule-coverage 100% · ceiling Documented

This project has two README files: one SimTong Android landing page with an MVP status and a module/architecture diagram, and another fastlane documentation that installs Fastlane, lists distribute/actions (android test/beta/deploy), and links to the Fastlane docs. The SimTong README is mostly branding content; there is no architecture description, no setup instructions beyond xcode-select install, no configuration or dependency details, and no usage of the Android framework itself. The fastlane README is a valid tool doc but does not describe how to build/run the app.

What to do

Improve Documentation Quality — currently 4.0/10. — This project has two README files: one SimTong Android landing page with an MVP status and a module/architecture diagram, and another fastlane documentation that installs Fastlane, lists distribute/actions (android test/beta/deploy), and links to the Fastlane docs. The SimTong README is mostly branding content; there is no architecture description, no setup instructions beyond xcode-select install, no configuration or dependency details, and no usage of the Android framework itself. The fastlane README is a valid tool doc but does not describe how to build/run the app.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D21 · Naming Consistency / 10Exemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)7.1 / 10Strong✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 7.1 / 10 · rule-coverage 100% · ceiling Documented

2 finding(s): 0 critical, 2 high, 0 medium, 0 low.

High: github-actions-mutable-action-tag · ×2.github/workflows/ci.yml:15detected by semgrep finding

What to do

Resolve the 2 High finding(s) in Static Analysis (SAST) — start with ci.yml (2). — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

79 of 79 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is feature/feature-mypage/src/main/java/com/comit/feature_mypage/screen/PrivacyPolicyScreen.kt.

Dormant codebase

What to do

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.

Do you agree with this assessment?

D35 · Change Coupling8.2 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: 2_SignUpVerifyScreen.kt↔3_SignUpPasswordScreen.kt 90%; 1_SignUpNameScreen.kt↔2_SignUpVerifyScreen.kt 90%; 2_SignUpVerifyScreen.kt↔4_SignUpNicknameScreen.kt 90%

Boundary-crossing change coupling: GetHolidayViewModel.kt ↔ RemoteHolidayDataSourceImpl.kt · ×3feature/feature-home/src/main/java/com/comit/feature_home/vm/GetHolidayViewModel.kt

Change coupling: 2_SignUpVerifyScreen.kt ↔ 3_SignUpPasswordScreen.kt · ×6feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/2_SignUpVerifyScreen.kt

Change coupling clique: AuthFindScreen.kt, FindPasswordEmailCodeScreen.kt, FindPasswordFixPasswordScreen.ktfeature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/find/AuthFindScreen.kt

What to do

Resolve the 3 Boundary-crossing change coupling finding(s) in Change Coupling — start with GetHolidayViewModel.kt, SimTongCalendar.kt, SimTongCalendarDialog.kt. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 6 Change coupling finding(s) in Change Coupling — start with 2_SignUpVerifyScreen.kt (2), 1_SignUpNameScreen.kt, SimTongCalendarGetList.kt. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with AuthFindScreen.kt. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D38 · OSV Dependency Vulnerabilities6.5 / 10Adequate✓ Tool-verified

What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.

Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.

Maturity: Documented → Verified → Prevented · effective 6.5 / 10 · rule-coverage 100% · ceiling Documented

7 finding(s): 0 critical, 5 high, 2 medium, 0 low.

High CVE: [GHSA redacted] · ×5Gemfile.lockdetected by osv-scanner finding

Medium CVE: [GHSA redacted] · ×2Gemfile.lockdetected by osv-scanner finding

What to do

Resolve the 5 High CVE finding(s) in OSV Dependency Vulnerabilities — start with Gemfile.lock (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 2 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with Gemfile.lock (2). — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

M1 · Documentation (README)4.7 / 10Weak✓ Tool-verified

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.

The root README is 38 words — likely missing build/run/architecture context.

What to do

Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add a README to the 16 of 16 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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).

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

Do you agree with this assessment?

M4 · Documentation accuracy5.0 / 10Adequate◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

README claims 'MVP service' while the evidence shows a complete project tree (292 source files)

What to do

Reconcile the README with reality: README claims 'MVP service' while the evidence shows a complete project tree (292 source files).

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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.

Do you agree with this assessment?

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

Lens	Score	Rating	Impact
Code Health	95%	Exemplary	Strongest area.
Architecture	82%	Strong	Solid.
Maturity	45%	Weak — gated by D34, M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	57%	Adequate — gated by P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	79%	Strong	Solid.

Not included — 74 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over 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
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — 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
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 — ~158 lines of test source are present (.kt) 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 Gradle version catalogue and a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)), 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 (.kt) 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 Gradle version catalogue and a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — 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 — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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 .kt, 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 (.kt) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 121 value object(s); a Domain/Aggregates/ValueObjects layer
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
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
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 — the Gradle `jacocoTestReport` task) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from 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.

Issue — 10 finding(s)

D38 · OSV Dependency Vulnerabilities · High CVE · ×5

High CVE: [GHSA redacted] Gemfile.lock — addressable 2.8.1: [GHSA redacted] — upgrade to 2.9.0
High CVE: [GHSA redacted] Gemfile.lock — faraday 1.10.2: [GHSA redacted] — upgrade to 1.10.6. This is 1 of 2 advisories with a published fix this scan raises against faraday 1.10.2, and their fixed versions do not agree — anything below 1.10.6 still leaves at least one of them open. Take this package to 1.10.6 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against faraday 1.10.2: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] Gemfile.lock — jwt 2.5.0: [GHSA redacted] — upgrade to 2.10.3
High CVE: [GHSA redacted] Gemfile.lock — rexml 3.2.5: [GHSA redacted] — upgrade to 3.3.6. This is 1 of 6 advisories with a published fix this scan raises against rexml 3.2.5, and their fixed versions do not agree — anything below 3.3.9 still leaves at least one of them open. Take this package to 3.3.9 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against rexml 3.2.5: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] Gemfile.lock — webrick 1.7.0: [GHSA redacted] — upgrade to 1.8.2. This one row stands for the 2 advisories this scan raises against webrick 1.7.0: [GHSA redacted], [GHSA redacted].

D35 · Change Coupling · Boundary-crossing change coupling · ×3

Boundary-crossing change coupling: GetHolidayViewModel.kt ↔ RemoteHolidayDataSourceImpl.kt feature/feature-home/src/main/java/com/comit/feature_home/vm/GetHolidayViewModel.kt — `feature/feature-home/src/main/java/com/comit/feature_home/vm/GetHolidayViewModel.kt` (context feature) and `remote/src/main/java/com/comit/remote/datasource/RemoteHolidayDataSourceImpl.kt` (context remote) sit in DIFFERENT parts of the tree yet change together 64% of the time (7 of the 11 commits that touched the less-changed of the two, renames followed) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Boundary-crossing change coupling: SimTongCalendar.kt ↔ HolidayAPI.kt feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendar.kt — `feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendar.kt` (context feature) and `remote/src/main/java/com/comit/remote/api/HolidayAPI.kt` (context remote) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched the less-changed of the two, renames followed) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Boundary-crossing change coupling: SimTongCalendarDialog.kt ↔ WriteScheduleScreen.kt common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt — `common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt` (context common-compose) and `feature/feature-home/src/main/java/com/comit/feature_home/screen/schedule/WriteScheduleScreen.kt` (context feature) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched the less-changed of the two, renames followed) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.

D29 · Static Analysis (SAST) · High · ×2

High: github-actions-mutable-action-tag .github/workflows/ci.yml:15 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v2`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v2 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:17 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-java@<40-character SHA>`. This step references `actions/setup-java@v2`; resolve the SHA it points at today with `gh api repos/actions/setup-java/commits/v2 --jq .sha`.

Warning — 28 finding(s)

D35 · Change Coupling · Change coupling · ×6

Change coupling: 2_SignUpVerifyScreen.kt ↔ 3_SignUpPasswordScreen.kt feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/2_SignUpVerifyScreen.kt — `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/2_SignUpVerifyScreen.kt` and `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/3_SignUpPasswordScreen.kt` change together 90% of the time (9 of the 10 commits that touched the less-changed of the two, renames followed). 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: 1_SignUpNameScreen.kt ↔ 2_SignUpVerifyScreen.kt feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/1_SignUpNameScreen.kt — `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/1_SignUpNameScreen.kt` and `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/2_SignUpVerifyScreen.kt` change together 90% of the time (9 of the 10 commits that touched the less-changed of the two, renames followed). 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: 2_SignUpVerifyScreen.kt ↔ 4_SignUpNicknameScreen.kt feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/2_SignUpVerifyScreen.kt — `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/2_SignUpVerifyScreen.kt` and `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/4_SignUpNicknameScreen.kt` change together 90% of the time (9 of the 10 commits that touched the less-changed of the two, renames followed). 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: SimTongCalendarGetList.kt ↔ GetHolidayViewModel.kt feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendarGetList.kt — `feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendarGetList.kt` and `feature/feature-home/src/main/java/com/comit/feature_home/vm/GetHolidayViewModel.kt` change together 73% of the time (8 of the 11 commits that touched the less-changed of the two, renames followed) 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 (that is what the inversion buys) and the thing to add is a comment saying so, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking.
Change coupling: WriteClosedDayScreen.kt ↔ GetHolidayViewModel.kt feature/feature-home/src/main/java/com/comit/feature_home/screen/WriteClosedDayScreen.kt — `feature/feature-home/src/main/java/com/comit/feature_home/screen/WriteClosedDayScreen.kt` and `feature/feature-home/src/main/java/com/comit/feature_home/vm/GetHolidayViewModel.kt` change together 64% of the time (7 of the 11 commits that touched the less-changed of the two, renames followed) 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 (that is what the inversion buys) and the thing to add is a comment saying so, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking.
Change coupling: 3_SignUpPasswordScreen.kt ↔ 4_SignUpNicknameScreen.kt feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/3_SignUpPasswordScreen.kt — `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/3_SignUpPasswordScreen.kt` and `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/4_SignUpNicknameScreen.kt` change together 62% of the time (8 of the 13 commits that touched the less-changed of the two, renames followed). 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.

D38 · OSV Dependency Vulnerabilities · Medium CVE · ×2

Medium CVE: [GHSA redacted] Gemfile.lock — aws-sdk-s3 1.117.1: [GHSA redacted] — upgrade to 1.208.0
Medium CVE: [GHSA redacted] Gemfile.lock — excon 0.93.1: [GHSA redacted] — upgrade to 1.5.0

D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2

Duplicated block (19 lines × 2) common-compose/src/main/java/com/comit/common/BtnField.kt:104 — common-compose/src/main/java/com/comit/common/BtnField.kt:104-122 | core-design-system/src/main/java/com/comit/core_design_system/component/TextField.kt:183-201 — 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 `common-compose/src/main/java/com/comit/common/BtnField.kt:104` 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 (19 lines × 2) core-design-system/src/main/java/com/comit/core_design_system/component/Vote.kt:329 — core-design-system/src/main/java/com/comit/core_design_system/component/Vote.kt:329-347 | core-design-system/src/main/java/com/comit/core_design_system/component/Vote.kt:352-370 — 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. 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.

D1 · Cyclomatic Complexity · FixPasswordKt.FixPassword (cyclomatic 21) · ×1

FixPasswordKt.FixPassword (cyclomatic 21) feature/feature-mypage/src/main/java/com/comit/feature_mypage/screen/fix/password/FixPassword.kt:68 — FixPasswordKt.FixPassword has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · SimTongApiCallKt.simTongApiCall (cyclomatic 19) · ×1

SimTongApiCallKt.simTongApiCall (cyclomatic 19) data/src/main/java/com/comit/data/util/SimTongApiCall.kt:39 — SimTongApiCallKt.simTongApiCall has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · SimTongCalendarGetListKt.organizeList (cyclomatic 19) · ×1

SimTongCalendarGetListKt.organizeList (cyclomatic 19) feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendarGetList.kt:26 — SimTongCalendarGetListKt.organizeList has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D16 · Bus Factor · dormant codebase · ×1

dormant codebase — no living knowledge left to concentrate — All 79 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).

D2 · Cognitive Complexity · SimTongCalendarGetListKt.organizeList (cognitive 31) · ×1

SimTongCalendarGetListKt.organizeList (cognitive 31) feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendarGetList.kt:26 — SimTongCalendarGetListKt.organizeList has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18, loops 11, boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SimTongCalendarKt.SimTongCalendarItem (cognitive 17) · ×1

SimTongCalendarKt.SimTongCalendarItem (cognitive 17) feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendar.kt:368 — SimTongCalendarKt.SimTongCalendarItem has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15, boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D3 · God Classes · FileTooLong · ×1

FileTooLong: typography/typography.kt core-design-system/src/main/java/com/comit/core_design_system/typography/typography.kt:0 — FileTooLong — 515 significant lines (blank, comment-only and punctuation-only lines excluded). 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.

D35 · Change Coupling · Change coupling clique · ×1

Change coupling clique: AuthFindScreen.kt, FindPasswordEmailCodeScreen.kt, FindPasswordFixPasswordScreen.kt feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/find/AuthFindScreen.kt — 3 files — `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/find/AuthFindScreen.kt`, `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/find/password/FindPasswordEmailCodeScreen.kt`, `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/find/password/FindPasswordFixPasswordScreen.kt` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.

D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1

Duplicated block (17 lines × 2) common-compose/src/main/java/com/comit/common/BtnField.kt:74 — common-compose/src/main/java/com/comit/common/BtnField.kt:74-90 | core-design-system/src/main/java/com/comit/core_design_system/component/TextField.kt:128-144 — 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 `common-compose/src/main/java/com/comit/common/BtnField.kt:74` 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.

D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1

Duplicated block (16 lines × 3) feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/1_SignUpNameScreen.kt:311 — feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/1_SignUpNameScreen.kt:311-326 | feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/2_SignUpVerifyScreen.kt:59-74 | feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/3_SignUpPasswordScreen.kt:152-167 — 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 `feature/feature-onboarding/src/main/java/com/comit/feature_auth/screen/signUp/1_SignUpNameScreen.kt:311` 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.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1

Duplicated block (16 lines × 2) core-design-system/src/main/java/com/comit/core_design_system/typography/typography.kt:456 — core-design-system/src/main/java/com/comit/core_design_system/typography/typography.kt:456-471 | core-design-system/src/main/java/com/comit/core_design_system/typography/typography.kt:563-578 — 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 `core-design-system/src/main/java/com/comit/core_design_system/typography/typography.kt:456` 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.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1

Duplicated block (15 lines × 2) feature/feature-home/src/main/java/com/comit/feature_home/screen/WriteClosedDayScreen.kt:259 — feature/feature-home/src/main/java/com/comit/feature_home/screen/WriteClosedDayScreen.kt:259-273 | feature/feature-home/src/main/java/com/comit/feature_home/screen/alarm/AlarmScreen.kt:33-47 — 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 `feature/feature-home/src/main/java/com/comit/feature_home/screen/WriteClosedDayScreen.kt:259` 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.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1

Duplicated block (14 lines × 2) feature/feature-home/src/main/java/com/comit/feature_home/screen/schedule/ShowScheduleScreen.kt:200 — feature/feature-home/src/main/java/com/comit/feature_home/screen/schedule/ShowScheduleScreen.kt:200-213 | feature/feature-home/src/main/java/com/comit/feature_home/screen/schedule/ShowScheduleScreen.kt:267-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `feature/feature-home/src/main/java/com/comit/feature_home/screen/schedule/ShowScheduleScreen.kt:200` 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.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1

Duplicated block (11 lines × 2) common-compose/src/main/java/com/comit/common/SimImageUploadLayout.kt:53 — common-compose/src/main/java/com/comit/common/SimImageUploadLayout.kt:53-63 | feature/feature-mypage/src/main/java/com/comit/feature_mypage/screen/MyPageScreen.kt:214-224 — 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 `common-compose/src/main/java/com/comit/common/SimImageUploadLayout.kt:53` 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.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1

Duplicated block (10 lines × 2) common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt:97 — common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt:97-106 | feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendar.kt:101-110 — 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.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1

Duplicated block (9 lines × 2) common-util/src/main/java/com/comit/common/unit/bitmap.kt:13 — common-util/src/main/java/com/comit/common/unit/bitmap.kt:13-21 | core-design-system/src/main/java/com/comit/core_design_system/util/bitmap.kt:13-21 — 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 `common-util/src/main/java/com/comit/common/unit/bitmap.kt:13` 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.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1

Duplicated block (8 lines × 2) common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt:147 — common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt:147-154 | common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt:168-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt:147` 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.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1

Duplicated block (6 lines × 2) common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt:342 — common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt:342-348 | feature/feature-home/src/main/java/com/comit/feature_home/calendar/SimTongCalendarGetList.kt:35-40 — 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 `common-compose/src/main/java/com/comit/common/dialog/SimTongCalendarDialog.kt:342` 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.

Recommendation — 3 finding(s)

D11 · Test Reliability · Test reliability not included · ×1

Test reliability not included — Test source is present (.kt) 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.

D34 · Knowledge Freshness · Dormant codebase · ×1

Dormant codebase — 79 of 79 significant files have no living knowledge — the codebase as a whole is dormant, not 79 separate risks. Re-engage owners or document before change.

D8 · Code Coverage · Coverage not included · ×1

Coverage not included — suite not readable by the collector — Coverage NOT MEASURED: test source is present (.kt) 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 — the Gradle `jacocoTestReport` task) 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 manifests (a Gradle version catalogue and a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) were found, but this pass cannot parse them 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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --json --quiet --timeout 0 --metrics off .	2	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	none (no readable dependency manifest)	—	none (no readable dependency manifest): not present in this environment	0	—
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.	0	—
D33 · JS/npm Dependency Vulnerabilities	trivy	—	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.	0	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	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.	0	—
D38 · OSV Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive .	7	artifacts/raw/osv-scanner.json
D40 · Network Egress Confinement	runtime-hardening	—	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.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	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.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	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 019fc9ff-f22f-785f-87d6-dfe9e6fee2d1 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency matrix

At a glance — Code Health · 95% · Exemplary

At a glance — Architecture · 82% · Strong

At a glance — Maturity · 45% · Weak · gated by D34, M2

At a glance — Readiness · 57% · Adequate · gated by P3

At a glance — Security · 79% · Strong

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts