Blowfish cipher
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
Blowfish uses a 64-bit block and is vulnerable to birthday attacks (Sweet32) on long streams; prefer AES-GCM.
Why it matters
Blowfish uses a 64-bit block, which makes it vulnerable to Sweet32 birthday collisions once enough data is encrypted under one key. It is a dated choice with no advantage over modern ciphers. New designs should not select it.
How to fix it
Use AES-256 (128-bit block) in GCM mode, or ChaCha20-Poly1305. Both are faster on modern hardware and avoid the small-block problem. Note that bcrypt, which is built on Blowfish internally for password hashing, is a separate and still-acceptable use and is not what this flags.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo