Sobelow.Crypto.WeakHash (Sobelow v0.18.1)
View SourceWeak or inappropriate hashing
MD4, MD5 and SHA-1 are unsuitable when collision resistance is required. RIPEMD-160 is reported as a legacy choice, not as a proven collision break. Prefer SHA-256 or stronger for security-sensitive digests. Non-security checksums and cache keys may legitimately use legacy hashes.
Only the algorithm is inspected, never the names of the values being hashed, so a fast hash used for password storage is not reported.
Legacy hashes receive medium confidence in controllers and low elsewhere. HMAC-MD5 receives low confidence as a legacy construction; HMAC-SHA1 is not flagged merely because unkeyed SHA-1 has collision attacks. Dynamic algorithm values are not resolved. Calls with literal data, inline captures and pipes are included.
References: https://www.rfc-editor.org/rfc/rfc6151
$ mix sobelow -i Crypto.WeakHash