Kilo Code
Website
Kilo is the all-in-one agentic engineering platform. Build, ship, and iterate faster with the most popular open source coding agent.
Is Kilo Code safe? Promising trust profile, but some evidence still deserves review.
Compare Kilo Code
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: Kilo Code scores 66.6/100 (Grade B), ranked #459 of 1378 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.1/10; 33% of recent commits are signed; no published advisory affects its latest release (kilocode); last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →
What Kilo Code can reach, and who runs it
Checked 2026-10-06, each with its source. PUBLISHER is the company's or project's own statement, which we haven't verified; CHECKED is something we observed ourselves. These facts describe the product. They don't change its score.
Who runs it
- PUBLISHER Run by Anaconda, Inc. with its affiliate Kilo Code Inc.
Where your data goes
- PUBLISHER Paid plans can switch off retention of AI prompts and outputs, with controls over which model providers requests are routed to.
Security practice
- PUBLISHER SOC 2 documentation is available in its trust center, trust.kilo.ai. The page doesn't say which report type.
- CHECKED kilo.ai publishes a security.txt ([email protected]), and the repository has a SECURITY.md.
How Kilo Code could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 81.3 A · #10 of 77
- Raise the OSSF Scorecard from 5.1 to 9.0lowest checks: CII-Best-Practices 0, Dangerous-Workflow 0, Fuzzing 0 +8.2 → 74.8 B · #12 of 77
- Sign every commit33% signed today +3.4 → 70.0 B · #17 of 77
Chain of custody
Scanners check what the code says. This traces who ships Kilo Code and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/Kilo-Org/kilocode, MIT, last pushed 2026-10-17. 33% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.1/10 (scanned Oct 2, 2026, refresh pending). The checks that decide who can get a change released:
- Code Review8
- Branch Protection4
- Signed Releases0
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies1
All 18 Scorecard checks
Binary-Artifacts 9Branch-Protection 4CI-Tests 10CII-Best-Practices 0Code-Review 8Contributors 10Dangerous-Workflow 0Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 1SAST 10Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages Not linked
- npm kilocode No source link declared No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: kilocode 1.2.0. No published advisory affects it (OSV, checked 2026-10-17).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Kilo Code.
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Kilo Code’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Kilo Code compares in Coding Agents
- #23 Open Interpreter 67.4 +0.8
- #24 Open SWE 66.8 +0.2
- #25 Kilo Code 66.6 this agent
- #26 Crush 66.4 −0.2
- #27 DeepSeek-Reasonix 65.5 −1.1
Bars show each HVTrust score; the tick marks Kilo Code’s 66.6.
Where the 66.6 comes from
HVTrust dimensions vs the Coding Agents average
66.6 / 100 · 100.0% confidenceKilo Code Coding Agents average (77 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
92.9 / 100Common questions about Kilo Code
Does Kilo Code publish package provenance?
Does Kilo Code have an OpenSSF Scorecard?
Is Kilo Code actively maintained?
What license does Kilo Code use?
Are Kilo Code's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Kilo Code's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Kilo Code?
For maintainers
HVTrust scores Kilo 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/kilo-code)
<a href="https://hvtracker.net/agents/kilo-code"><img src="https://hvtracker.net/badge/kilo-code.svg" alt="HVTrust"></a>
Other agents in Coding Agents
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON