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/rephrase-0.2/rephrase.c

FINAL RESULTS:

data/rephrase-0.2/rephrase.c:253:5:  [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.
    execv (path, argv);
data/rephrase-0.2/rephrase.c:355:9:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
        printf (s->b ? " %d" : "%d", s->try[s->b] + 1);
data/rephrase-0.2/rephrase.c:57:3:  [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 *command[ARGS_MAX + 1];
data/rephrase-0.2/rephrase.c:96:3:  [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 *argv[ARGS_MAX + 1];
data/rephrase-0.2/rephrase.c:103:3:  [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 pattern[PATTERN_MAX + 1];
data/rephrase-0.2/rephrase.c:118:18:  [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).
  if (!(tty_fp = fopen ("/dev/tty", "r+"))) {
data/rephrase-0.2/rephrase.c:346:19:  [2] (misc) open:
  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).
  if ((dev_null = open ("/dev/null", O_RDWR)) == -1) {
data/rephrase-0.2/rephrase.c:136:28:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    while (!(s->io_count = read (fileno (tty_fp), s->pattern + s->i, 1))) {
data/rephrase-0.2/rephrase.c:153:30:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
      while (!(s->io_count = read (fileno (tty_fp), s->pattern, 1))) {

ANALYSIS SUMMARY:

Hits = 9
Lines analyzed = 484 in approximately 0.02 seconds (22093 lines/second)
Physical Source Lines of Code (SLOC) = 422
Hits@level = [0]  21 [1]   2 [2]   5 [3]   0 [4]   2 [5]   0
Hits@level+ = [0+]  30 [1+]   9 [2+]   7 [3+]   2 [4+]   2 [5+]   0
Hits/KSLOC@level+ = [0+] 71.09 [1+] 21.327 [2+] 16.5877 [3+] 4.73934 [4+] 4.73934 [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.