Skip to content
DevUtils Online

Workflow Automation

keep vs n8n-skills

n8n-skills leads by 9.7 · clear

A

keep

81.6

12,531 stars · license n/a

keep versus n8n-skills is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. keep is written mainly in Python; n8n-skills is written mainly in Shell. The composite score is 81.6 for keep and 91.3 for n8n-skills.

keep has 12,531 GitHub stars to n8n-skills's 6,662, a gap of 5,869 (1.88×). Forks are 1,555 for keep and 1,084 for n8n-skills. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 95.

Push history: keep was last pushed on 16 November 2026 (1 day ago), and n8n-skills was last pushed on 24 October 2026 (24 days ago). Open issues stand at 708 for keep (0.056 per star) and 22 for n8n-skills (0.003 per star). Issue-health scores are 52 and 96; activity scores are 100 and 78.

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. n8n-skills 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. License scores in this pair are 30 for keep and 96 for n8n-skills. This is a procurement signal, not legal advice.

Only n8n-skills is marked self-hostable here (6,662 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: keep is unpriced in this catalog, n8n-skills is open source.

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

n8n-skills finishes ahead at 91.3 against keep at 81.6, a 9.7 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.

keep versus n8n-skills metrics
Signal keep n8n-skills
GitHub stars 12,531 6,662
Forks 1,555 1,084
Open issues 708 22
Adoption 100 93
Activity 100 78
Community 100 95
Issue health 52 96
License 30 96
Self-hosting 35 100
Composite 81.6 91.3

Questions this page answers

Which has more GitHub stars, keep or n8n-skills?

keep has more GitHub stars: 12,531 versus 6,662 for n8n-skills. The gap is 5,869 stars.

Which was updated more recently, keep or n8n-skills?

keep was pushed more recently: 16 November 2026 versus 24 October 2026 for n8n-skills. That is 23 days apart.

Can I self-host both keep and n8n-skills?

Only n8n-skills is marked self-hostable. keep is not.

Which license is easier to embed in a commercial product, keep or n8n-skills?

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. n8n-skills 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.

Who wins the keep vs n8n-skills score?

n8n-skills scores 91.3 and keep scores 81.6. This page calls that a clear lead for n8n-skills.

Related comparisons