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/wmtemp-0.0.6/temp.h Examining data/wmtemp-0.0.6/dockapp.h Examining data/wmtemp-0.0.6/xpm/xpm.h Examining data/wmtemp-0.0.6/temp.c Examining data/wmtemp-0.0.6/main.c Examining data/wmtemp-0.0.6/dockapp.c FINAL RESULTS: data/wmtemp-0.0.6/temp.c:38: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 str[256]; data/wmtemp-0.0.6/temp.c:46:7: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). f = fopen(filename, "r"); ANALYSIS SUMMARY: Hits = 2 Lines analyzed = 1061 in approximately 0.05 seconds (20715 lines/second) Physical Source Lines of Code (SLOC) = 788 Hits@level = [0] 57 [1] 0 [2] 2 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 59 [1+] 2 [2+] 2 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 74.8731 [1+] 2.53807 [2+] 2.53807 [3+] 0 [4+] 0 [5+] 0 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.