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/dbar-0.0.20100524/dbar.c FINAL RESULTS: data/dbar-0.0.20100524/dbar.c:135: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 aval[MAXLEN], *endptr; data/dbar-0.0.20100524/dbar.c:149:16: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range (CWE-190). If source untrusted, check both minimum and maximum, even if the input had no minus sign (large numbers can roll over into negative number; consider saving to an unsigned value if that is intended). maxchars = atoi(argv[i]); ANALYSIS SUMMARY: Hits = 2 Lines analyzed = 198 in approximately 0.03 seconds (6102 lines/second) Physical Source Lines of Code (SLOC) = 93 Hits@level = [0] 7 [1] 0 [2] 2 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 9 [1+] 2 [2+] 2 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 96.7742 [1+] 21.5054 [2+] 21.5054 [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.