Kiro Crew
Website
A persistent workspace for development work that self-improves and continues beyond one session.
Is Kiro Crew safe? Promising trust profile, but some evidence still deserves review.
Compare Kiro Crew
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: Kiro Crew scores 62.7/100 (Grade C), ranked #562 of 1343 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.2/10; 100% of recent commits are signed; last pushed 2026-10-01. Every point is earned from checkable signals — never paid placement. How scoring works →
How Kiro Crew 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.
- Raise the OSSF Scorecard from 5.2 to 9.0lowest checks: Binary-Artifacts 0, CII-Best-Practices 0, Fuzzing 0 +7.9 → 70.6 B · #17 of 75
How Kiro Crew compares in Coding Agents
- #26 GitHub Copilot CLI 63.5 +0.8
- #27 Archon 62.8 +0.1
- #28 Kiro Crew 62.7 this agent
- #29 oh-my-openagent 62.7 ±0
- #30 Kimi Code 60.8 −1.9
Bars show each HVTrust score; the tick marks Kiro Crew’s 62.7.
Where the 62.7 comes from
HVTrust dimensions vs the Coding Agents average
62.7 / 100 · 100.0% confidenceKiro Crew Coding Agents average (75 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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
85.1 / 100Supply Chain Trust
Common questions about Kiro Crew
Does Kiro Crew publish package provenance?
Does Kiro Crew have an OpenSSF Scorecard?
Is Kiro Crew actively maintained?
What license does Kiro Crew use?
Are Kiro Crew'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 →
- browser
- shell
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Kiro Crew'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 Kiro Crew?
For maintainers
HVTrust scores Kiro Crew 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/kiro-crew)
<a href="https://hvtracker.net/agents/kiro-crew"><img src="https://hvtracker.net/badge/kiro-crew.svg" alt="HVTrust"></a>
Other agents in Coding Agents
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON