gchq/CyberChef

Prefer this fork if your main workflow is security-analysis-centric and you want built-in VT/YARA helpers. Prefer upstream if you want an actively maintained, broader-purpose CyberChef with current fixes and features.

Prefer upstream unless you specifically need the fork's crypto/blockchain additions. This fork looks attractive for niche wallet, key, certificate, and decompression workflows, but its long lag and divergence make it a poorer default choice for general adoption.

Choose upstream unless you specifically need a frozen 2023 snapshot; this fork appears inactive, adds no visible capabilities, and is far behind current CyberChef.

Choose this fork if Chinese localization is the main requirement and you value a friendlier local UX over staying current with upstream. Avoid it if you need the newest CyberChef capabilities, active maintenance, or a low-risk base for long-term adoption.

Prefer upstream unless you specifically need an old frozen snapshot. This fork offers no visible enhancements, is heavily outdated, and is a poor choice for active use or adoption.

Prefer upstream unless you specifically need an untouched, historical snapshot. This fork adds no visible capabilities and is far behind current CyberChef, so it is a poor adoption choice for most users.

Choose upstream unless you specifically need an old frozen snapshot. This fork does not show meaningful added capability and is too far behind to recommend for active use.

Prefer upstream unless you specifically need the older frozen state. This fork adds no visible functionality and is substantially behind, so it is a poor adoption choice for active use.

Choose this fork if RISC-V or esolang support is the reason you are adopting CyberChef. Choose upstream if you want the freshest general-purpose CyberChef with lower lag and fewer merge risks.