Week 45, updated 2 Nov 2026

Coding agents KiroCrew

Is KiroCrew safe?

Short answer: Caution. StackGrade's weekly scan of kirodotdev/KiroCrew gives it a Caution label for 2 critical-severity known vulnerabilities in runtime dependencies (OSV). It does list 10 high-severity advisories in runtime dependencies, which don't change the label. 8 phrases in agent instruction files were flagged for human review (unclear). Critical advisories are counted once per package; a known issue in a locked package version does not prove KiroCrew is exploitable in your setup. Automated scan of commit ed7b18a on 2 Nov 2026, not a manual audit.

Updated : the last week its score, rank or safety result changed.

Persistent workspace for development work that continues beyond a single agent session.

  • 4,717 stars
  • pushed 2 Nov
  • Apache-2.0
  • Python

github.com/kirodotdev/KiroCrew · kiro.dev/crew

52score out of 100

#27of 52 overall#8in Coding agents▲ 4 vs Week 44

  • Maintenance 30%92
  • Adoption 30%1
  • Docs 20%69
  • Community 20%–
W42W43W44W45

Score over the last 4 weeks: 50, 44, 48, 52.

Caution

2 critical-severity known vulnerabilities in runtime dependencies (OSV).

How this score works

Each part is a percentile among all 52 tracked tools, so 50 is average for this list. Community is not measured yet; the score uses the other 80%.

  • Maintenance: Last push 2 Nov 2026. Last 10 GitHub releases within 3 days (about 91 per 30 days), latest release 2 Nov 2026. Median 1.5 h to close an issue (8 closed issues).
  • Adoption: 4,717 stars (70%), 930 forks (30%).
  • Docs: README 192,116 characters, 17 headings, 9 code blocks, install section: yes.

Methodology

#8 of 14 in Coding agents

Ranked by score. The yellow row is this tool.

Coding agents, Week 45score 0–100, safety
  1. 1Gemini CLI#4 overall70Caution
  2. 2OpenCode#5 overall70No issues found
  3. 3OpenHands#10 overall68Caution
  4. 4Claude Code#11 overall65No dependencies scanned
  5. 5Cline#12 overall65Caution
  6. 6Codex#16 overall58Caution
  7. 7deepseek-harness#17 overall57Caution
  8. 8KiroCrew#27 overall52Caution
Show the other 6
  1. 9magpie#28 overall51No issues found
  2. 10Continue#43 overall37Caution
  3. 11goose#44 overall36Caution
  4. 12Aider#45 overall31Caution
  5. 13codex-plugin-cc#48 overall29No issues found
  6. 14Roo Code#51 overall23Caution

Safety scan, 2 Nov 2026

Automated scan of commit ed7b18a, 20,153 files. Not a manual audit.

Caution

  • 2Critical dependency advisories10 high, 9 medium, 1 low. OSV, runtime dependencies only.
  • 2Install hooksnpm scripts that run on install; none downloads remote content.
  • 0Remote-code patternsFor example eval(fetch(…)).
  • 139Agent files checked8 phrases flagged for review.
  • 10curl | sh installersIn docs or program code. Information only.
Why this label?

Why this label:

  • 2 critical-severity known vulnerabilities in runtime dependencies (OSV)

Known vulnerabilities in runtime dependencies (OSV): 2 critical, 10 high, 9 medium, 1 low

  • anyio@4.9.0 (PYSEC-2026-4025) in src/kiro_crew/apps/builtins/aws_control/crew/runtime/container/requirements.txt
  • certifi@2026.7.22 (PYSEC-2026-4320) in src/kiro_crew/apps/builtins/aws_control/crew/runtime/container/requirements.txt

Also found (informational, does not change the label):

  • 8 injection-related phrases in instruction files, flagged for human review (often defensive guidance), e.g. skills/gateway-restart/SKILL.md
  • 10 high-severity known vulnerabilities in runtime dependencies (OSV)
  • 2 npm install hooks, none downloading remote content
  • Program code runs a curl|sh style installer (14 occurrences, e.g. cli.sh)
  • Documents curl|sh style installer (10 occurrences, e.g. .github/workflows/publish-installer.yml)
  • Skill scripts contact: 127.0.0.1

Notes:

  • 20 affected packages only in dev/test/docs manifests, not counted
  • Telemetry/analytics references in code: telemetry, mixpanel, amplitude

Automated scan of commit ed7b18a on 2 Nov 2026, not a manual audit. 20,153 files checked. What we check

Repo activity

From the GitHub API, fetched 2 Nov 2026.

  • 10+Releases, 90 daysLatest v0.12.0-rc.4, 2 Nov
  • 2hMedian issue closeOver 8 closed issues
  • 4.7kStars+140 since 26 Oct
  • 930Forks2,983 open issues
  • 2026Repo created16 Jul 2026
30 days ago2 Nov
10 releases in the last 30 days, one mark each (GitHub releases feed, last 10 entries).

10 releases in the last 30 days (GitHub releases feed, last 10 entries):

Questions about KiroCrew

Answers use this week's StackGrade data.

Is KiroCrew safe to use?

Caution. StackGrade's weekly scan of kirodotdev/KiroCrew gives it a Caution label for 2 critical-severity known vulnerabilities in runtime dependencies (OSV). It does list 10 high-severity advisories in runtime dependencies, which don't change the label. 8 phrases in agent instruction files were flagged for human review (unclear). Critical advisories are counted once per package; a known issue in a locked package version does not prove KiroCrew is exploitable in your setup. Automated scan of commit ed7b18a on 2 Nov 2026, not a manual audit.

How does StackGrade score KiroCrew?

KiroCrew scores 52 out of 100 in Week 45: #27 of 52 tracked tools overall and #8 in Coding agents. The score combines maintenance (92), adoption (1) and docs (69) as percentiles among all 52 tracked tools; community (20% weight) is not measured yet, so the score uses the other 80%. It is not a hands-on test and it is separate from the safety label.

What are the alternatives to KiroCrew?

The highest-scored other tools in Coding agents this week: Gemini CLI (70, Caution), OpenCode (70, No issues found), OpenHands (68, Caution), Claude Code (65, No dependencies scanned). StackGrade has not tested them hands-on.

What licence does KiroCrew use?

The licence listed for kirodotdev/KiroCrew is Apache-2.0. Read the licence text before commercial use.

Compare and use it

All facts and sources
Type
AI tool
License
Apache-2.0
Language
Python
Created
16 Jul 2026
Owner
kirodotdev (Organization)
Forks
930

GitHub description: “A persistent workspace for development work that self-improves and continues beyond one session.”

Sources: github.com/kirodotdev/KiroCrew, api.github.com/repos/kirodotdev/KiroCrew, raw.githubusercontent.com/kirodotdev/KiroCrew/main/README.md. Fetched 2 Nov 2026.

Know when KiroCrew changes label

One email a week: the new top 10, the biggest score changes and every safety label that changed.

Free. Double opt-in: you confirm by email first, unsubscribe in one click.