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/libxfixes-5.0.3/include/X11/extensions/Xfixes.h
Examining data/libxfixes-5.0.3/src/Selection.c
Examining data/libxfixes-5.0.3/src/Cursor.c
Examining data/libxfixes-5.0.3/src/Xfixesint.h
Examining data/libxfixes-5.0.3/src/Xfixes.c
Examining data/libxfixes-5.0.3/src/Region.c
Examining data/libxfixes-5.0.3/src/SaveSet.c

FINAL RESULTS:

data/libxfixes-5.0.3/src/Cursor.c:156:21:  [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).
    int				nbytes = strlen (name);
data/libxfixes-5.0.3/src/Cursor.c:232: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).
    int				    nbytes = strlen (name);

ANALYSIS SUMMARY:

Hits = 2
Lines analyzed = 1557 in approximately 0.05 seconds (31042 lines/second)
Physical Source Lines of Code (SLOC) = 1126
Hits@level = [0]   0 [1]   2 [2]   0 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   2 [1+]   2 [2+]   0 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 1.7762 [1+] 1.7762 [2+]   0 [3+]   0 [4+]   0 [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.