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/haskell-posix-pty-0.2.2/cbits/fork_exec_with_pty.c
Examining data/haskell-posix-pty-0.2.2/cbits/fork_exec_with_pty.h
Examining data/haskell-posix-pty-0.2.2/cbits/pty_size.c
Examining data/haskell-posix-pty-0.2.2/cbits/pty_size.h

FINAL RESULTS:

data/haskell-posix-pty-0.2.2/cbits/fork_exec_with_pty.c:78:21:  [4] (shell) execvp:
  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.
        if (search) execvp(file, argv);
data/haskell-posix-pty-0.2.2/cbits/fork_exec_with_pty.c:79:21:  [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.
        else        execv(file, argv);

ANALYSIS SUMMARY:

Hits = 2
Lines analyzed = 160 in approximately 0.02 seconds (9130 lines/second)
Physical Source Lines of Code (SLOC) = 109
Hits@level = [0]   0 [1]   0 [2]   0 [3]   0 [4]   2 [5]   0
Hits@level+ = [0+]   2 [1+]   2 [2+]   2 [3+]   2 [4+]   2 [5+]   0
Hits/KSLOC@level+ = [0+] 18.3486 [1+] 18.3486 [2+] 18.3486 [3+] 18.3486 [4+] 18.3486 [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.