I could see developing a checklist of things to look for during code review. It might be fairly tedious since you’d probably need to scrutinize each line. Code

I could see developing a checklist of things to look for during code review. It might be fairly tedious since you’d probably need to scrutinize each line. Code review guidelines or style guides come close to being checklists. There are also various kinds of static analysis like CheckStyle, FindBugs, etc. that check for common mistakes. Of course, statically typed languages have type checking built in that prevents mistakes. Plenty of languages already have type systems and/or object constructs prevent the class of problems that led to Heartbleed (bounds checked arrays IIRC).