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 64.7/100 (Grade C), ranked #547 of 1387 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.9/10; 100% of recent commits are signed; last pushed 2026-11-15. 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.9 to 9.0lowest checks: Binary-Artifacts 0, CII-Best-Practices 0, Fuzzing 0 +6.4 → 71.1 B · #15 of 77
Chain of custody
Scanners check what the code says. This traces who ships Kiro Crew and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/kirodotdev/KiroCrew, Apache-2.0, last pushed 2026-11-15. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.9/10 (scanned Nov 13, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection5
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies8
All 18 Scorecard checks
Binary-Artifacts 0Branch-Protection 5CI-Tests 10CII-Best-Practices 0Code-Review 10Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 8SAST 9Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. Kiro Crew is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-09-02 OSSF Scorecard: 5.3/10
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Kiro Crew’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 Kiro Crew compares in Coding Agents
- #25 Kilo Code 65.7 +1.0
- #26 Ponytail 65.3 +0.6
- #27 Kiro Crew 64.7 this agent
- #28 Archon 63.9 −0.8
- #29 Kimi Code 63.5 −1.2
Bars show each HVTrust score; the tick marks Kiro Crew’s 64.7.
Where the 64.7 comes from
HVTrust dimensions vs the Coding Agents average
64.7 / 100 · 100.0% confidenceKiro Crew 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 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
86.2 / 100Common 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