01Evaluates cryptographic library ergonomics and algorithm selection patterns
02Provides 'Pit of Success' rationales to replace insecure legacy patterns
03Detects 'footgun' API designs that invite developer misuse or security bypasses
04Audits configuration schemas for dangerous defaults and silent failure modes
052 GitHub stars
06Identifies 'stringly-typed' security risks like manual SQL or command concatenation