head to head · open source

composio vs LockKnife

composio has 30,405 GitHub stars, 4,842 forks, 88 open issues and last shipped today. LockKnife has 542 stars, 120 forks, 3 open issues and last shipped 23 days ago. composio leads on adoption by 5,510% (30,405 vs 542 stars). composio is written in TypeScript under MIT; LockKnife is written in Python under GPL-3.0. composio has attracted 16% as many forks as stars, LockKnife 22%. composio was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (ai-agents, developer-tools), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

composio ★ 30K LockKnife ★ 542 category Developer Tools

← all 20902 open source comparisons

Side by side

composio LockKnife
GitHub stars ★ 30K ★ 542
License MIT GPL-3.0
Written in TypeScript Python
Last push 2026-10-03 2026-09-10
Forks ⑂ 4.8K ⑂ 120
Self-hosting Yes Yes
Data ownership Your server Your server

pick composio if

  • You weight community size — 30K stars and counting
  • You want the MIT license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full composio profile →

pick LockKnife if

  • You want the LockKnife feature set and don't need the biggest community
  • You prefer the GPL-3.0 license terms
  • Your stack matches Python
  • You evaluated both and LockKnife fits your workflow better

full LockKnife profile →

About composio

Composio is an MIT licensed agent toolkit platform, distributed as TypeScript and Python SDKs, that gives AI agents more than 1,000 pre authenticated toolkits, per user sessions, authentication, triggers, and a sandbox for turning intent into action across real applications.

read the full composio overview →

About LockKnife

LockKnife is a unified Android security research toolkit that gives forensic investigators, penetration testers, and reverse engineers a case driven TUI workspace and a headless CLI for extraction, credential recovery, APK analysis, runtime inspection, and reporting from one framework.

read the full LockKnife overview →

More in Developer Tools

ECC ★ 271K react ★ 251K OpenCode ★ 212K vscode ★ 193K Langflow ★ 155K pi ★ 112K

Related comparisons

openclaw vs langflow ecc vs react ecc vs langflow react vs langflow ecc vs supabase react vs supabase n8n vs langflow ecc vs puppeteer openclaw vs openhands openclaw vs paperclip hermes-agent vs pi hermes-agent vs openhands hermes-agent vs paperclip opencode vs pi opencode vs openhands opencode vs paperclip react vs vscode react vs neovim react vs zed opencode vs neovim opencode vs zed vscode vs neovim vscode vs zed react vs kilocode

More Frameworks & Platforms projects

Compare either of these against the rest of the Frameworks & Platforms field.

composio vs ECC composio vs react composio vs Langflow composio vs Supabase composio vs puppeteer composio vs archify composio vs PocketBase composio vs i-have-adhd composio vs codebase-memory-mcp composio vs herdr composio vs ToolJet composio vs AppSmith

Frequently asked questions

Is composio or LockKnife more popular?

composio has 30,405 GitHub stars and LockKnife has 542. composio has the larger community by that measure.

Are composio and LockKnife free?

Both are open source. composio is licensed under MIT and LockKnife under GPL-3.0. Neither carries a licence fee.

What is the difference between composio and LockKnife?

composio is written in TypeScript and LockKnife in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, composio or LockKnife?

Choose composio if you want the larger community (30,405 stars) or its MIT licence terms. Choose LockKnife if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.