eve-software-factory-template vs adk-recipes
Two of the top agent backends, side by side: score, setup, license, activity and what each review found.
eve-software-factory-template
eve pipeline that turns GitHub or Linear issues into reviewed draft PRs
adk-recipes
Runnable Agent Development Kit recipes, from single patterns to deployable agents
| What we compare | eve-software-factory-template | adk-recipes |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 46, known | 75, popular |
| Freshness | 100, active | 100, active |
| Maintenance | 35, patchy | 66, fair |
| Easy to run | 67, easy | 0, hard |
| Agent-ready | 70, partly | 30, minimal |
| Facts from GitHub and the README | ||
| Stars | 1.2k | 10.4k |
| License | MIT (permissive) | Apache-2.0 (permissive) |
| Last commit | Sep 2026 | Oct 2026 |
| Last release | None published | None published |
| Language | TypeScript | Python |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
eve-software-factory-template
An eve pipeline named Foreman: label an issue factory, @mention it, or delegate from Linear, and four agents (classifier, analyst, implementer, reviewer) each run in their own sandbox and end with a draft pull request on FACTORY_REPO. The reviewer sees only the pushed branch, a factory brain keeps notes about your repo between runs, and it deploys to Vercel with GitHub and Linear connectors. For teams piloting agent-written PRs with human merge.
Who it is for: Teams piloting agent-written pull requests with human merge
Strengths
- Reviewer is isolated from the implementer; verdicts are made against the real diff
- Six entry points including red-CI self-repair on factory branches only
- Local dev TUI treats runs as untrusted; GitHub writes wait for approval
- Separate docs site; CLAUDE.md and AGENTS.md included
Weaknesses
- Tied to eve, Vercel Connect, Vercel Sandbox and Vercel Blob
- No model provider named in the README; model access comes through the Vercel stack
- No tests listed
- First task fails if the GitHub App cannot reach FACTORY_REPO; the error surfaces late
- TypeScript, eve, ai-sdk
- Needs vercel, github-app-connector, linear-connector, vercel-blob
- GitHub template
- env example file
adk-recipes
A recipe collection for Google's Agent Development Kit: core/ holds single-pattern agents (OAuth flows, session memory, guardrails, RAG), contrib/ holds deployable vertical agents targeting Agent Engine, Cloud Run and Gemini Enterprise, and plugins/ holds skills packaged with SKILL.md and EVAL.yaml. Each recipe has its own README; ADK SDKs exist for Python, TypeScript, Go, Java and Kotlin. For teams standardizing on ADK and Google Cloud.
Who it is for: Teams standardizing on ADK and Google Cloud
Strengths
- Core recipes isolate one pattern each, so they lift cleanly into your project
- Vertical agents include deploy paths to Agent Engine and Cloud Run
- Recipe checklist and handbook define a contribution standard; tests and AGENTS.md included
- Committed within the last day
Weaknesses
- Root README is an index; no single app, no shared setup
- Gemini and Google Cloud are the assumed model and deploy target
- README states recipes are demonstrations, not for production use
- Mixed languages and maturity across folders
- Python, google, google-adk
- Needs google-adk, google-api-key-or-vertex-ai