Learn how Kilo and Void differ in their key features, development activity, technology stack and community adoption, so you can decide which of these tools is best for you.
Last 30 days
Last commit
Repository age
Version
License
Repository

Last 30 days
This repository was archived by the owner and is no longer maintained.
Last commit
Repository age
License
Repository

Kilo appears to have several advantages over Void, particularly in growth, activity and licensing. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Both Kilo and Void show comparable community engagement with 27,019 and 28,827 stars respectively. In terms of developer contributions, Kilo has 3,089 forks, indicating strong developer engagement.
Kilo is growing faster, adding 468 stars in the last 30 days (+1.8%) against losing 29 stars for Void (-0.1%). Kilo is the smaller project of the two, so it is closing the gap rather than extending a lead.
Kilo shows more recent development activity with its last commit 13 hours ago, while Void was last updated 3 months ago. This suggests Kilo is being more actively maintained.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash, Typescript, JSX, Python, Next.js, Golang, PHP. However, they differ in their additional technology choices: Void leverages SCSS, Rust, C, Objective-C, Java, Swift, C++, Ruby, MATLAB, C#, Perl, Lua, Dart, Clojure, CoffeeScript, R, Visual Basic .NET.
Both projects started around the same time, with Kilo beginning 1 year ago and Void 2 years ago.
Kilo uses the MIT license, which is more permissive than Void's Apache-2.0 license, potentially offering greater flexibility for commercial use and integration.
Kilo also focuses on AI Coding Agents, IDEs & Code Editors while Void extends into AI Coding Assistants, AI-Powered Editors.