Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers and small teams who already run multiple coding agents and want persistent specialist roles, parallel handoffs, and worktree isolation instead of re-explaining repo context to one generalist session on every task.
Who should use it
Who should skip it
Avoid running getcrew44/crew44 in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
getcrew44/crew44 is tracked by RepoRadar as a app in the AI Agents / Orchestration section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for getcrew44/crew44 are workflow potential (10.0) and maturity (9.3), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned getcrew44/crew44 a composite score of 8.7 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 360.0 and never affects the composite score or tier. The risk label of 'medium' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Crew44 coordinates real coding-agent runtimes that can read files, edit code, and run commands in your repo, so the actual blast radius is still set by the underlying runtime permissions and model configuration; State lives under local project folders and ~/.crew44, so teams should review what chat logs, skills, and verification artifacts are retained before using it on sensitive client code; The workflow is strongest when you already have multiple agent CLIs installed; users expecting an all-in-one hosted model experience will still need to bring their own runtimes and model access.