A · leads
edict
89.9
17,077 stars · MIT
Workflow Automation
edict leads by 10.4 · clear
A · leads
89.9
17,077 stars · MIT
B
79.5
2,639 stars · MIT
edict versus shepherd is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 89.9 for edict and 79.5 for shepherd.
edict has 17,077 GitHub stars to shepherd's 2,639, a gap of 14,438 (6.47×). Forks are 1,771 for edict and 227 for shepherd. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 73.
Push history: edict was last pushed on 28 September 2026 (50 days ago), and shepherd was last pushed on 09 September 2026 (69 days ago). Open issues stand at 15 for edict (0.001 per star) and 13 for shepherd (0.005 per star). Issue-health scores are 96 and 96; activity scores are 58 and 58.
Both edict and shepherd are listed as MIT. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both edict (17,077 stars) and shepherd (2,639 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: edict is open source, shepherd is open source.
edict is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 27 points (100 vs 73), and the tightest is self-hosting at 0 points (100 vs 100).
edict finishes ahead at 89.9 against shepherd at 79.5, a 10.4 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | edict | shepherd |
|---|---|---|
| GitHub stars | 17,077 | 2,639 |
| Forks | 1,771 | 227 |
| Open issues | 15 | 13 |
| Adoption | 100 | 81 |
| Activity | 58 | 58 |
| Community | 100 | 73 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.9 | 79.5 |
🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System — 9 specialized AI agents with real-time dashboard, model config, and full audit trails
A runtime substrate that turns an agent's execution into a reversible, Git-like trace, so meta-agents can observe, fork, replay, and revert any run. Couples agent and environments in a copy-on-write fork ~5x faster than docker commit, with ~95% KV-cache reuse on replay. Framework built for meta-agents to supervise, optimize, and train other agents
edict has more GitHub stars: 17,077 versus 2,639 for shepherd. The gap is 14,438 stars.
edict was pushed more recently: 28 September 2026 versus 09 September 2026 for shepherd. That is 19 days apart.
Yes. This catalog marks both edict and shepherd as self-hostable. Confirm each project's deploy docs before you plan a migration.
edict is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. shepherd is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
edict scores 89.9 and shepherd scores 79.5. This page calls that a clear lead for edict.