Skip to content
DevUtils Online

Workflow Automation

edict vs keep

edict leads by 9.6 · clear

A · leads

edict

89.9

17,077 stars · MIT

B

keep

80.3

12,531 stars · license n/a

edict versus keep 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 80.3 for keep.

edict has 17,077 GitHub stars to keep's 12,531, a gap of 4,546 (1.36×). Forks are 1,771 for edict and 1,555 for keep. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 98.

Push history: edict was last pushed on 28 September 2026 (50 days ago), and keep was last pushed on 16 November 2026 (1 day ago). Open issues stand at 15 for edict (0.001 per star) and 708 for keep (0.056 per star). Issue-health scores are 96 and 52; activity scores are 58 and 100.

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. keep is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for edict and 30 for keep. This is a procurement signal, not legal advice.

Only edict is marked self-hostable here (17,077 stars, deploy score 100). keep is not (12,531 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: edict is open source, keep is unpriced in this catalog.

The lead is split. edict is furthest ahead on license flexibility (96 to 30), while keep is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.

edict finishes ahead at 89.9 against keep at 80.3, a 9.6 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

edict versus keep metrics
Signal edict keep
GitHub stars 17,077 12,531
Forks 1,771 1,555
Open issues 15 708
Adoption 100 97
Activity 58 100
Community 100 98
Issue health 96 52
License 96 30
Self-hosting 100 35
Composite 89.9 80.3

edict

🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System — 9 specialized AI agents with real-time dashboard, model config, and full audit trails

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, edict or keep?

edict has more GitHub stars: 17,077 versus 12,531 for keep. The gap is 4,546 stars.

Which was updated more recently, edict or keep?

keep was pushed more recently: 16 November 2026 versus 28 September 2026 for edict. That is 49 days apart.

Can I self-host both edict and keep?

Only edict is marked self-hostable. keep is not.

Which license is easier to embed in a commercial product, edict or keep?

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. keep is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the edict vs keep score?

edict scores 89.9 and keep scores 80.3. This page calls that a clear lead for edict.

Related comparisons