Kilo Code
Tracked across 29 snapshots (2026-01-27 → 2026-06-12).
Rating timeline
Dimension trajectory
Autonomy
12/20Integration
15/20Context
10/20Compliance
10/20Viability
10/20Interface
14/20Cap timeline
Notable events
- 2026-02-18Jump+6 rating
- 2026-02-26Cap +acquisition-uncertainty
- 2026-04-20Cap −acquisition-uncertainty
- 2026-05-16Cap +unvalidated-benchmarks
- 2026-05-16Cap +acquisition-uncertainty
- 2026-05-18Cap −unvalidated-benchmarks
- 2026-06-10Drop-8 rating
What would move this next
Upgrade if: SOC 2 Type II or ISO 27001 achieved (compliance 10→12+, status candidate); GitLab ROFR expires Aug 24 2026 without exercise (remove acquisition-uncertainty cap, viability could move to 11); Series A funding announced (viability 10→11-12); F500-class named customer confirmed; independent end-to-end benchmark (SWE-bench Verified or Aider Leaderboard) entry published (autonomy could move toward 16). Downgrade if: GitLab exercises ROFR (acquisition disruption, viability/compliance downward pressure); reliability/token-burn complaints intensify to a widespread pattern (reliability-complaints cap on autonomy, autonomy≤12); code indexing regresses again; Martian open-source result disputed or not reproduced.