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/xf86-input-multitouch-1.0~rc3/driver/multitouch.c
Examining data/xf86-input-multitouch-1.0~rc3/include/button.h
Examining data/xf86-input-multitouch-1.0~rc3/include/capabilities.h
Examining data/xf86-input-multitouch-1.0~rc3/include/common.h
Examining data/xf86-input-multitouch-1.0~rc3/include/gestures.h
Examining data/xf86-input-multitouch-1.0~rc3/include/hwstate.h
Examining data/xf86-input-multitouch-1.0~rc3/include/memory.h
Examining data/xf86-input-multitouch-1.0~rc3/include/mtouch.h
Examining data/xf86-input-multitouch-1.0~rc3/include/mtstate.h
Examining data/xf86-input-multitouch-1.0~rc3/include/xbypass.h
Examining data/xf86-input-multitouch-1.0~rc3/src/capabilities.c
Examining data/xf86-input-multitouch-1.0~rc3/src/gestures.c
Examining data/xf86-input-multitouch-1.0~rc3/src/hwstate.c
Examining data/xf86-input-multitouch-1.0~rc3/src/memory.c
Examining data/xf86-input-multitouch-1.0~rc3/src/mtouch.c
Examining data/xf86-input-multitouch-1.0~rc3/src/mtstate.c
Examining data/xf86-input-multitouch-1.0~rc3/src/test.c

FINAL RESULTS:

data/xf86-input-multitouch-1.0~rc3/include/xbypass.h:9:2:  [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, format, args);
data/xf86-input-multitouch-1.0~rc3/src/capabilities.c:27:25:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination
  [MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
  snprintf (warning: strncat is easily misused).
#define ADDCAP(s, c, x) strcat(s, c->has_##x ? " " #x : "")
data/xf86-input-multitouch-1.0~rc3/driver/multitouch.c:92:11:  [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.
	unsigned char btmap[DIM_BUTTON + 1] = {
data/xf86-input-multitouch-1.0~rc3/include/capabilities.h:30: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 devname[32];
data/xf86-input-multitouch-1.0~rc3/src/capabilities.c:156: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 line[1024];
data/xf86-input-multitouch-1.0~rc3/src/test.c:57:11:  [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).
	int fd = open(argv[1], O_RDONLY | O_NONBLOCK);

ANALYSIS SUMMARY:

Hits = 6
Lines analyzed = 2008 in approximately 0.06 seconds (32291 lines/second)
Physical Source Lines of Code (SLOC) = 1344
Hits@level = [0]   4 [1]   0 [2]   4 [3]   0 [4]   2 [5]   0
Hits@level+ = [0+]  10 [1+]   6 [2+]   6 [3+]   2 [4+]   2 [5+]   0
Hits/KSLOC@level+ = [0+] 7.44048 [1+] 4.46429 [2+] 4.46429 [3+] 1.4881 [4+] 1.4881 [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.