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/coq-8.12.0/kernel/byterun/coq_memory.h Examining data/coq-8.12.0/kernel/byterun/coq_uint63_native.h Examining data/coq-8.12.0/kernel/byterun/coq_fix_code.h Examining data/coq-8.12.0/kernel/byterun/coq_float64.h Examining data/coq-8.12.0/kernel/byterun/coq_uint63_emul.h Examining data/coq-8.12.0/kernel/byterun/coq_interp.h Examining data/coq-8.12.0/kernel/byterun/coq_values.h Examining data/coq-8.12.0/kernel/byterun/coq_values.c Examining data/coq-8.12.0/kernel/byterun/coq_fix_code.c Examining data/coq-8.12.0/kernel/byterun/coq_memory.c Examining data/coq-8.12.0/kernel/byterun/coq_interp.c Examining data/coq-8.12.0/ide/ide_win32_stubs.c Examining data/coq-8.12.0/dev/build/windows/patches_coq/ln.c Examining data/coq-8.12.0/dev/build/windows/patches_coq/pkg-config.c Examining data/coq-8.12.0/dev/header.c FINAL RESULTS: data/coq-8.12.0/dev/build/windows/patches_coq/pkg-config.c:28:12: [4] (shell) execv: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. return execv("/usr/bin/pkgconf", argvnew); data/coq-8.12.0/dev/build/windows/patches_coq/pkg-config.c:20:5: [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 * argvnew[argc+2]; ANALYSIS SUMMARY: Hits = 2 Lines analyzed = 3092 in approximately 2.87 seconds (1079 lines/second) Physical Source Lines of Code (SLOC) = 2482 Hits@level = [0] 12 [1] 0 [2] 1 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 14 [1+] 2 [2+] 2 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 5.64061 [1+] 0.805802 [2+] 0.805802 [3+] 0.402901 [4+] 0.402901 [5+] 0 Dot directories skipped = 2 (--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.