Skip to main content
Kyro is an open-source product fromTonmoy InfrastructureOwned byEshan Roy
Tonmoy Infrastructure • Owned by Eshan Roy

Contributing to Kyro

Kyro is an open-source product from Tonmoy Infrastructure, owned and architected by Eshan Roy. We welcome contributions from developers, designers, technical writers, and testers of all skill levels. Follow this guide to set up your environment, run checks, and submit pull requests.

1. Development Setup

Clone the repository and install Node dependencies:

Terminal
git clone https://github.com/eshanized/Kyro.git
cd Kyro
npm install
Prerequisites: Node.js ≥ 20.x, Rust ≥ 1.75.0 (rustc, cargo, rustfmt, clippy).

2. Common Makefile Targets

Kyro includes a versatile Makefile for standard development workflows:

Terminal
# Run full desktop app (Vite UI + Rust native backend)
make dev

# Run Vite frontend only in browser at http://localhost:1420 (rapid UI styling)
make dev-ui

# Run full desktop app with verbose debug logging
make dev-debug

# Run headless under virtual X11 framebuffer (Linux / CI)
make dev-headless

3. Testing & Verification Pipeline

Before submitting a pull request, all automated checks must pass locally. Kyro provides a unified command:

Terminal
make verify

This single command automatically validates:

  • make fmt-check: Rust code formatting validation (rustfmt)
  • make clippy: Rust Clippy linter with strict warning enforcement (-D warnings)
  • make test: Over 230 Rust unit, integration, and security regression tests
  • make test-ui: 60+ frontend Vitest test suites and TypeScript compiler check (tsc --noEmit)
  • make build-ui: Production frontend bundle build verification

4. Conventional Commit Standards

We enforce Conventional Commits for automated changelogs:

Commit Message Format
<type>(<scope>): <short description>

Examples:
feat(ui): add visual artifact comparison slider
fix(governance): prevent unverified shell expansions in executor
test(audit): add regression tests for element inspection
docs(runtime): update connector authentication flow

5. Pull Request Checklist