Is Kimi Code safe to use?

Kimi Code has an HVTrust score of 59.0/100 (Grade C), ranked #349 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Kimi Code?

Kimi Code scores 59.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 6.4k GitHub stars and is categorized under Coding Agents.

Kimi Code

MoonshotAI/kimi-code

Kimi Code CLI — The Starting Point for Next-Gen Agents

Coding Agents TypeScript Grade C Listed MIT

59.0/100

Rank #349 of 1283

Compare Kimi Code

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-11 · 0d ago

Recent change

Rank +1

Is Kimi Code safe? Kimi Code scores 59.0/100 (Grade C), ranked #349 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.8/10; 100% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#28 GitHub Copilot CLI — 59.3 (C) → #29 Nanocoder — 59.2 (C) → #31 DeepCode — 58.7 (C) → #32 Pi — 58.1 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 16 spots (#332 → #348)

2026-08-08

Rank Moved

Rank dropped 87 spots (#246 → #333)

2026-07-14

Rank Moved

Rank dropped 14 spots (#221 → #235)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.8/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Kimi Code View Coding Agents Report missing data

86.8

Activity sub-score · out of 100

#30

In Coding Agents

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

6.4k

Forks

1.0k

Last Push

2026-08-11

today

Commits (4 wk)

376

Downloads (7d)

—

HN mentions (30d)

Open Issues

626

Rank Change

▼1

was #348

Analysis

HVTrust Dimensions vs Coding Agents

59.0 / 100 · 100.0% confidence

Kimi Code Coding Agents average (67 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.5 / 25

0.8 above avg 7.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

10.9 / 17

in line with avg 11.1

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

4.7 above avg 15.3

AdoptionLog-scaled stars · package downloads

9.1 / 20

3.1 below avg 12.2

Activity Inputs

86.8 / 100

StarsRepository reach

22.8 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.8 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 4

Branch-Protection 3

CI-Tests 9

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Kimi Code safe?

Kimi Code has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Kimi Code publish package provenance?

No published build provenance is currently detected for Kimi Code. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Kimi Code have an OpenSSF Scorecard?

Kimi Code has an OpenSSF Scorecard score of 2.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Kimi Code actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Kimi Code use?

Kimi Code ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Kimi Code's commits signed?

100% of the last 100 commits to Kimi Code are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Kimi Code?

For maintainers

HVTrust scores Kimi Code from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-10

Rank Moved

Rank dropped 16 spots (#332 → #348)

2026-08-08

Rank Moved

Rank dropped 87 spots (#246 → #333)

2026-07-14

Rank Moved

Rank dropped 14 spots (#221 → #235)

2026-07-13

Rank Moved

Rank dropped 28 spots (#193 → #221)

2026-06-24

Rank Moved

Rank dropped 16 spots (#164 → #180)

2026-06-10

Scorecard Added

OSSF Scorecard: 3.2/10

2026-06-10

Grade Changed

Trust grade D → C

2026-06-10

Rank Moved

Rank rose 58 spots (#192 → #134)

2026-06-10

HVTrust Changed

HVTrust up 24.2pts (34.8 → 59.0)

2026-06-08

Newly Listed

First tracked at rank #195

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/kimi-code.svg)](https://hvtracker.net/agents/kimi-code)
            
HTML:
            <a href="https://hvtracker.net/agents/kimi-code"><img src="https://hvtracker.net/badge/kimi-code.svg" alt="HVTrust"></a>

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON