KaiCode: 9th Open Source Festival

In KaiCode’26 we received 153 applications. After a three-phase review of them, the jury rewarded the following projects and the steering committee agreed:

The RAprogramm/yew-nav-link project (6★), a navigation-link library for the Yew framework in Rust with automatic active-state detection, demonstrated perfect software development practices: clean and idiomatic code, requirements captured as formal specifications and architecture decision records, strict static analysis (clippy, CodeQL, Scorecard, zizmor), mutation, fuzz, and property testing with enforced 95% coverage, an mdBook documentation site, semantic-versioned releases with a maintained changelog, protected branching, and exemplary REUSE-compliant licensing. Source files are small, meticulously documented, and every file carries SPDX headers. $2048 was the reward.

The Ahoo-Wang/Wow project (296★), a reactive CQRS and Event-Sourcing microservice framework built on Domain-Driven Design, written in Kotlin, showed us an excellent codebase: clean, modular DDD/CQRS design, genuine multi-reviewer code review, Testcontainers-backed integration testing, enforced coverage thresholds and detekt static analysis, a bilingual documentation site, and a long history of semantic-versioned releases on Maven Central. However, issue labeling is inconsistent across recent tickets. $1024 was the reward.

awesome The ChopLogic/chop-logic-components project (5★), a library of reusable React components and hooks written in TypeScript, showed us awesome coding practices: conventions enforced by Biome, Prettier, commitlint, and Husky git hooks, mutation testing with Stryker on top of Codecov-tracked coverage, a Storybook gallery published as a documentation site, and semantic-versioned releases to npm with a maintained changelog. However, pull requests are self-merged by the sole author without review, and licensing stops at a single MIT file, with no SPDX headers in the sources. $512 was the reward.

Steering Committee

@medvednikov

@sobolevn

Jury

Each member of the jury reviews up to four projects. In each review we expect to see “good”, “average”, or “bad” mark in front of every quality dimension listed above. The sum of all marks constitute the final mark of a project.

@asomsiko