sharp▌

Identifies error-prone APIs, configurations, and designs that enable developer security mistakes. \n \n Evaluates six categories of sharp edges: algorithm selection footguns, dangerous defaults, primitive vs. semantic APIs, configuration cliffs, silent failures, and stringly-typed security \n Provides a four-phase analysis workflow: surface identification, edge case probing, threat modeling against three adversary types (malicious, lazy, confused), and validation \n Includes severity classificat