# What Version Control System Does Kimi-Code Use? Git Repository Structure Explained

> Discover which version control system Kimi-Code uses. Learn about its Git repository structure and how it's managed within the MoonshotAI monorepo.

- Repository: [Moonshot AI/kimi-code](https://github.com/MoonshotAI/kimi-code)
- Tags: internals
- Published: 2026-07-29

---

**Kimi-Code uses Git as its version control system, with repository metadata confirmed through the `.git` directory logs and multiple [`package.json`](https://github.com/MoonshotAI/kimi-code/blob/main/package.json) files declaring Git-specific source URLs across the MoonshotAI monorepo.**

MoonshotAI/kimi-code is managed entirely through Git, with definitive proof residing in both the repository's internal metadata and package configuration files. The presence of the `.git` directory alongside explicit Git URL declarations in [`package.json`](https://github.com/MoonshotAI/kimi-code/blob/main/package.json) files throughout the codebase confirms that Git powers all version control operations for this project. Understanding how Git is configured within this monorepo helps developers clone, fork, and contribute effectively.

## Evidence of Git in the Kimi-Code Source

### Git Metadata in the .git Directory

The `.git` directory at the repository root contains the complete Git metadata history. Specifically, `.git/logs/HEAD` records the initial clone operation from `https://github.com/MoonshotAI/kimi-code`, serving as the primary evidence that Git manages this codebase. This log file tracks all reference updates, including the source remote where the repository originated.

### Package.json Git Declarations

Multiple [`package.json`](https://github.com/MoonshotAI/kimi-code/blob/main/package.json) files throughout the monorepo explicitly declare Git as the version control system. In [`packages/tree-sitter-bash/package.json`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/tree-sitter-bash/package.json), the repository field specifies `"type": "git"` alongside `"url": "git+https://github.com/MoonshotAI/kimi-code.git"`. The root [`package.json`](https://github.com/MoonshotAI/kimi-code/blob/main/package.json) follows the same pattern, while [`pnpm-lock.yaml`](https://github.com/MoonshotAI/kimi-code/blob/main/pnpm-lock.yaml) references Git-based package resolutions, further cementing Git's role in dependency management.

## Verifying Git Configuration in Kimi-Code

You can confirm Git usage through both command-line tools and programmatic inspection of configuration files.

To verify the repository status and view recent activity:

```bash

# Confirm this is a Git repository

git rev-parse --is-inside-work-tree

# Output: true

# Display the current branch

git branch --show-current

# Output: main

# View recent commit history

git log -n 5 --oneline

```

To programmatically verify the Git URL from package configuration:

```typescript
import fs from 'fs';

// Read the Tree-sitter-Bash package configuration
const pkg = JSON.parse(
  fs.readFileSync('packages/tree-sitter-bash/package.json', 'utf8')
);

console.log(pkg.repository?.url);
// Output: git+https://github.com/MoonshotAI/kimi-code.git

```

## Summary

- **Git is the exclusive version control system** for MoonshotAI/kimi-code, as evidenced by the `.git` directory containing full metadata history.
- **Repository URLs in package.json files** explicitly declare `"type": "git"` with `git+https` protocols, confirming Git usage across the monorepo.
- **The `.git/logs/HEAD` file** records the original clone from GitHub, serving as definitive proof of Git initialization.
- **pnpm-lock.yaml references** Git-based package resolutions, integrating Git into the dependency management workflow.

## Frequently Asked Questions

### Is Kimi-Code hosted on GitHub?

Yes, Kimi-Code is hosted on GitHub at `https://github.com/MoonshotAI/kimi-code`. The `.git/logs/HEAD` file contains references to this remote URL, and multiple [`package.json`](https://github.com/MoonshotAI/kimi-code/blob/main/package.json) files point to the same GitHub repository, confirming GitHub as the hosting platform.

### Can I verify the Git configuration without cloning the repository?

While full verification requires access to the `.git` directory, you can inspect the repository metadata via the GitHub web interface. The [`package.json`](https://github.com/MoonshotAI/kimi-code/blob/main/package.json) files visible in the source tree declare Git as the version control type, and the presence of Git-specific files like `.gitignore` in the file listing indicates Git usage.

### Does the monorepo structure affect how Git works in Kimi-Code?

The monorepo organization uses standard Git operations across all packages. While individual packages like `tree-sitter-bash` contain their own [`package.json`](https://github.com/MoonshotAI/kimi-code/blob/main/package.json) files with Git declarations, the entire codebase is managed as a single Git repository with unified version control, not as separate repositories per package.

### What Git workflows are recommended for contributing to Kimi-Code?

Based on the repository structure, contributors should follow standard Git workflows including branching from `main`, making atomic commits, and pushing to personal forks before submitting pull requests. The `git+https` URLs in package files support both HTTPS and SSH authentication methods for cloning and contributing.