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/rotix-0.83/help.h
Examining data/rotix-0.83/rot.h
Examining data/rotix-0.83/help.c
Examining data/rotix-0.83/rotix.c
Examining data/rotix-0.83/rot.c

FINAL RESULTS:

data/rotix-0.83/rotix.c:193:5:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused).
				strcpy (arg, optarg);
data/rotix-0.83/rotix.c:33:9:  [3] (buffer) getopt_long:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
#define getopt_long(a, b, c, d, e) getopt(a, b, c)
data/rotix-0.83/rotix.c:33:36:  [3] (buffer) getopt:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
#define getopt_long(a, b, c, d, e) getopt(a, b, c)
data/rotix-0.83/rotix.c:94:12:  [3] (buffer) getopt_long:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
		option = getopt_long (argc, argv, "f:r:ao:t:LRhv", rotix_options, NULL);
data/rotix-0.83/rotix.c:76:2:  [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 rotme[2];
data/rotix-0.83/rotix.c:137:12:  [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).
					ifp = fopen (optarg, "r");
data/rotix-0.83/rotix.c:170:12:  [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).
					ofp = fopen (optarg, "a");
data/rotix-0.83/rotix.c:233:10:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older System
  V systems) (CWE-377).
			ifp = tmpfile ();
data/rotix-0.83/rotix.c:188:27:  [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).
				arg = (char *)malloc (strlen (optarg) + 1);
data/rotix-0.83/rotix.c:247:5:  [1] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused). Risk is low because the source is a constant character.
				strcpy (arg, "");
data/rotix-0.83/rotix.c:255:16:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
				rotme[0] = fgetc (stdin);
data/rotix-0.83/rotix.c:271:5:  [1] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused). Risk is low because the source is a constant character.
				strcpy (arg, "");
data/rotix-0.83/rotix.c:280:16:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
				rotme[0] = fgetc (ifp);
data/rotix-0.83/rotix.c:295:4:  [1] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused). Risk is low because the source is a constant character.
			strcpy (arg, "");
data/rotix-0.83/rotix.c:304:15:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
			rotme[0] = fgetc (ifp);

ANALYSIS SUMMARY:

Hits = 15
Lines analyzed = 460 in approximately 0.03 seconds (18370 lines/second)
Physical Source Lines of Code (SLOC) = 281
Hits@level = [0]  40 [1]   7 [2]   4 [3]   3 [4]   1 [5]   0
Hits@level+ = [0+]  55 [1+]  15 [2+]   8 [3+]   4 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 195.73 [1+] 53.3808 [2+] 28.4698 [3+] 14.2349 [4+] 3.55872 [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.