Is Kilo Code safe?
Kilo Code scores 60.9/100 (Grade C), ranked #197 of 418 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.2/10;
43% of recent commits are signed;
last pushed 2026-07-18. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
60.9/100 · Grade C
Strongest Signal
Maintenance
19.9/20
Weakest Signal
Safety / Integrity
8.7/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-15
Rank Moved
Rank dropped 10 spots (#188 → #198)
2026-07-14
Rank Moved
Rank dropped 11 spots (#177 → #188)
2026-07-13
Rank Moved
Rank dropped 22 spots (#155 → #177)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 5.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
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 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 →
Signals refreshed2026-07-19 08:02 UTC·Repo last pushed yesterday
Kilo 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 Kilo Code publish package provenance?
No published build provenance is currently detected for Kilo 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 Kilo Code have an OpenSSF Scorecard?
Kilo Code has an OpenSSF Scorecard score of 5.2/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 Kilo Code actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Kilo Code use?
Kilo Code ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Kilo Code's commits signed?
43% of the last 100 commits to Kilo 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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Marketplace
Marketplace plugin/integration surface detected.
browser
code
database
search
shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
How this surface has changed
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.
2026-06-18
Mcp Status Changed
Detected MCP server support changed: implemented → declared
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Google Gemini, OpenAI, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintain Kilo Code?
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.
