Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler. Number of rules (primarily dangerous function names) in C/C++ ruleset: 223 Examining data/terminal.app-0.9.9/charmaps.h Examining data/terminal.app-0.9.9/PreferencesWindowController.h Examining data/terminal.app-0.9.9/TerminalWindowPrefs.h Examining data/terminal.app-0.9.9/TerminalView.h Examining data/terminal.app-0.9.9/autokeyviewchain.h Examining data/terminal.app-0.9.9/Terminal.h Examining data/terminal.app-0.9.9/TerminalViewPrefs.h Examining data/terminal.app-0.9.9/PrefBox.h Examining data/terminal.app-0.9.9/TerminalParser_LinuxPrefs.h Examining data/terminal.app-0.9.9/TerminalParser_Linux.h Examining data/terminal.app-0.9.9/ServicesPrefs.h Examining data/terminal.app-0.9.9/Label.h Examining data/terminal.app-0.9.9/ServicesParameterWindowController.h Examining data/terminal.app-0.9.9/Services.h Examining data/terminal.app-0.9.9/TerminalWindow.h FINAL RESULTS: data/terminal.app-0.9.9/TerminalParser_Linux.h:33:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char input_buf[16]; data/terminal.app-0.9.9/TerminalParser_Linux.h:37:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char title_buf[TITLE_BUF_SIZE+1]; ANALYSIS SUMMARY: Hits = 2 Lines analyzed = 852 in approximately 0.04 seconds (24319 lines/second) Physical Source Lines of Code (SLOC) = 495 Hits@level = [0] 0 [1] 0 [2] 2 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 2 [1+] 2 [2+] 2 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 4.0404 [1+] 4.0404 [2+] 4.0404 [3+] 0 [4+] 0 [5+] 0 Dot directories skipped = 1 (--followdotdir overrides) Minimum risk level = 1 Not every hit is necessarily a security vulnerability. There may be other security vulnerabilities; review your code! See 'Secure Programming HOWTO' (https://dwheeler.com/secure-programs) for more information.