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/kcc-2.3/kcc.c

FINAL RESULTS:

data/kcc-2.3/kcc.c:375:5:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
    vfprintf(stderr, fmt, args);
data/kcc-2.3/kcc.c:123:1:  [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 shiftin[7] = "\033$B";
data/kcc-2.3/kcc.c:124:1:  [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 shiftout[4] = "\033(J";
data/kcc-2.3/kcc.c:181:18:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
	    if ((size = atoi(*v)) <= 0)
data/kcc-2.3/kcc.c:246:4:  [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(shiftin, "\033&@\033$B");
data/kcc-2.3/kcc.c:248:4:  [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(shiftin, "\033$%c", s[1]);
data/kcc-2.3/kcc.c:249: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(shiftout, "\033(%c", s[2]);
data/kcc-2.3/kcc.c:313:17:  [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 ((iop = fopen(*v, "r")) == NULL) {
data/kcc-2.3/kcc.c:408: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 str[LENLINE];
data/kcc-2.3/kcc.c:469: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 str[LENLINE];
data/kcc-2.3/kcc.c:619:35:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    for (s = str; --n > 0 && (c = getc(fp)) != EOF; )

ANALYSIS SUMMARY:

Hits = 11
Lines analyzed = 1428 in approximately 0.07 seconds (21743 lines/second)
Physical Source Lines of Code (SLOC) = 977
Hits@level = [0]   8 [1]   1 [2]   9 [3]   0 [4]   1 [5]   0
Hits@level+ = [0+]  19 [1+]  11 [2+]  10 [3+]   1 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 19.4473 [1+] 11.259 [2+] 10.2354 [3+] 1.02354 [4+] 1.02354 [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.