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/flexml-1.9.6/flexml-act-bootstrap.c Examining data/flexml-1.9.6/testbed/biparser.precious.c Examining data/flexml-1.9.6/testbed/init_header.h Examining data/flexml-1.9.6/examples/test.c FINAL RESULTS: data/flexml-1.9.6/flexml-act-bootstrap.c:95:10: [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). yyin = fopen(filename,"r"); data/flexml-1.9.6/testbed/biparser.precious.c:50:9: [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). infile=fopen("biparser-one.in","r"); data/flexml-1.9.6/testbed/biparser.precious.c:58:9: [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). infile=fopen("biparser-two.in","r"); data/flexml-1.9.6/examples/test.c:459:14: [1] (buffer) getc: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). (c = getc( yyin )) != EOF && c != '\n'; ++n ) \ ANALYSIS SUMMARY: Hits = 4 Lines analyzed = 1669 in approximately 0.12 seconds (13397 lines/second) Physical Source Lines of Code (SLOC) = 1098 Hits@level = [0] 21 [1] 1 [2] 3 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 25 [1+] 4 [2+] 3 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 22.7687 [1+] 3.64299 [2+] 2.73224 [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.