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/cpipe-3.0.1/cmdline.c
Examining data/cpipe-3.0.1/cmdline.h
Examining data/cpipe-3.0.1/cpipe.c

FINAL RESULTS:

data/cpipe-3.0.1/cpipe.c:207:6:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
     sprintf(buf, "%s ", cmd->prefix);
data/cpipe-3.0.1/cpipe.c:54:7:  [2] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf. Risk is low because the source has a constant maximum length.
      sprintf(buf, "%6.1fG", v*ONEGSCALE);
data/cpipe-3.0.1/cpipe.c:56:7:  [2] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf. Risk is low because the source has a constant maximum length.
      sprintf(buf, "%6.1fM", v*ONEMSCALE);
data/cpipe-3.0.1/cpipe.c:60:7:  [2] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf. Risk is low because the source has a constant maximum length.
      sprintf(buf, "%6.1fk", v*ONEkSCALE);
data/cpipe-3.0.1/cpipe.c:62:7:  [2] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf. Risk is low because the source has a constant maximum length.
      sprintf(buf, "%4.0f", v);
data/cpipe-3.0.1/cpipe.c:94: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 txt1[40], txt2[40], txt3[40];
data/cpipe-3.0.1/cpipe.c:155: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 txt1[40], txt2[40], txt3[40];
data/cpipe-3.0.1/cpipe.c:191: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 txt1[40], txt2[40], txt3[40];
data/cpipe-3.0.1/cpipe.c:106:13:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    bytes = read(STDIN_FILENO, buf, length-totalBytes);
data/cpipe-3.0.1/cpipe.c:206:25:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
     char *buf = malloc(strlen(cmd->prefix)+2);

ANALYSIS SUMMARY:

Hits = 10
Lines analyzed = 1136 in approximately 0.08 seconds (14658 lines/second)
Physical Source Lines of Code (SLOC) = 795
Hits@level = [0]  61 [1]   2 [2]   7 [3]   0 [4]   1 [5]   0
Hits@level+ = [0+]  71 [1+]  10 [2+]   8 [3+]   1 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 89.3082 [1+] 12.5786 [2+] 10.0629 [3+] 1.25786 [4+] 1.25786 [5+]   0
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.