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. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed today
Rank Trend
2026-06-022026-06-04
Activity & Reach
Stars
19.8k
Forks
2.6k
Last Push
2026-06-04
today
Commits (4 wk)
1311
Downloads (7d)
132
npm
HN mentions (30d)
9
Open Issues
1278
Rank Change
▲67
was #169
Analysis
HVTrust Dimensions
64.5 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
7.8 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.8 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
13.1 / 20
Activity Inputs
91.7 / 100
StarsRepository reach
25.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.9 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.0 / 10
via deps.dev · OpenSSF
Signed Commits
32%
of last 100 commits verified
Binary-Artifacts9
Branch-Protection4
CI-Tests10
CII-Best-Practices0
Code-Review9
Contributors10
Dangerous-Workflow0
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies0
SAST7
Security-Policy10
Signed-Releases0
Token-Permissions0
Vulnerabilities0
Is Kilo Code safe?
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.0/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?
32% 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OSSF Scorecard via deps.dev · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
