cryptgeonvsCyberChef
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| cryptgeon | CyberChef | |
|---|---|---|
| Score | 61/100 | 83/100 |
| Rank in category | #9 of 28 in File Sharing & Collaboration | #1 of 78 in Security |
| GitHub stars | 1 579 | 36 422 |
| Stars, last 30 days | +31 | +329 |
| Stable releases, 12 months | 2 | 12 |
| Latest release | v2.9.3 · 25 Jun 2026 | v11.5.0 · 18 Sept 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Svelte | JavaScript |
Which one should you pick?
CyberChef scores 83/100 against 61/100 for cryptgeon, so it is the safer default.
CyberChef ships more often: 12 stable releases in the past year, against 2 for cryptgeon.
If you want the quickest setup, CyberChef is easier to run; cryptgeon needs more configuration.
CyberChef is growing faster right now (+329 stars in 30 days).
Key differences
- License: cryptgeon is MIT, CyberChef is Apache-2.0.
- Language: cryptgeon is written mainly in Svelte, CyberChef in JavaScript.
- Features only cryptgeon lists: CLI Client, Client-side encryption, Configurable Limits, Custom theming and 8 more.
- Features only CyberChef lists: Automatic baking, Automatic encoding detection (Magic), Breakpoints and stepping, Byte offset highlighting and 8 more.
cryptgeon details →CyberChef details →