awesome-ai-engineering vs eko
awesome-ai-engineering is an agent project from dipakkr (MIT licence, 23k GitHub stars, last push 2026-10-21); eko is an agent project from FellouAI (MIT licence, 5.0k GitHub stars, last push 2026-03-03). They share 2 of 4 capabilities and integrations identified for either (overlap 0.50); only awesome-ai-engineering covers Model Fine-tuning; only eko covers Browser Control. Figures as of 2026-11-21. DER
awesome-ai-engineering profileeko profileOpen in the compare tool
Side-by-side facts
6 of 16 rows differ (marked). Unknown means no source we track states it.
| Field | awesome-ai-engineering | eko |
|---|---|---|
| Type | Agent project SRC | Agent project SRC |
| Publisher · differs | dipakkr SRC | FellouAI SRC |
| Licence | MIT SRC | MIT SRC |
| Open source | Yes DER | Yes DER |
| Pricing model | Unknown | Unknown |
| Hosting | Unknown | Unknown |
| Latest version | Unknown | Unknown |
| Languages · differs | Unknown | typescript SRC |
| GitHub stars · differs | 23k (22,608) SRC | 5.0k (4,963) SRC |
| Forks · differs | 4.9k SRC | 446 SRC |
| Last push · differs | 2026-10-21 SRC | 2026-03-03 SRC |
| Archived | No SRC | No SRC |
| First published · differs | 2018-09-17 SRC | 2024-11-23 SRC |
| Versions recorded | Unknown | Unknown |
| Verification | Auto-discovered; type inferred from repository topics HEU | Auto-discovered; type inferred from repository topics HEU |
| Last verified | Unknown | Unknown |
Shared and unique capabilitiesDER
Capabilities are assigned by keyword rules from each description unless a researcher set them; integrations are services named in the description or package metadata.
Both (2)
Only awesome-ai-engineering (1)
Only eko (1)
Platform compatibility
Status per platform from the evidence we hold. No pairing has been tested by AgentSidekick.
No compatibility evidence
For all 47 platforms on record the status is Unknown or Platform discontinued for both: neither product type implements a standard we can check (MCP, Agent Skills, Claude plugins) and neither publisher names a platform.
Maintenance
Repository activity read from the GitHub API. Activity is not quality.
| Measure | awesome-ai-engineering | eko |
|---|---|---|
| Status | Active DER | Slowing DER |
| Days since last push | 31 DER | 263 DER |
| Open issues | 42 SRC | 6 SRC |
| Latest GitHub release | Unknown | v4.1.0 · 2025-12-29 SRC |
| Newest registry version | Unknown | Unknown |
Evaluation dimensions
Separate signals with their evidence; there is no overall score. Hover or focus a status for its evidence.
| Dimension | awesome-ai-engineering | eko |
|---|---|---|
| Source authority | Auto-discovered | Auto-discovered |
| Publisher verification · differs | Not verified | Organisation account |
| Maintenance activity · differs | Active | Slowing |
| Licence clarity | MIT | MIT |
| Installation clarity | Unknown | Unknown |
| Documentation | Repository / website only | Repository / website only |
| Compatibility evidence | Unknown | Unknown |
| Security review | Not reviewed | Not reviewed |
Which fits which requirementDER
Derived from the differences above, one rule per line. Nothing here says either product is better; check the requirement against your own needs.
Choose awesome-ai-engineering if…
- you need Model Fine-tuning (classified for awesome-ai-engineering only)
- you require a repository pushed to in the last 90 days (awesome-ai-engineering: 2026-10-21; eko: 2026-03-03)
- you weigh adoption: 23k vs 5.0k GitHub stars (popularity, not quality)
Choose eko if…
- you need Browser Control (classified for eko only)
Sources
- awesome-ai-engineering · GitHub topic search: github.com (external)checked
- eko · GitHub topic search: github.com (external)checked
Page data last updated .