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/libx11-protocol-perl-0.56/eg/widgets.c

FINAL RESULTS:

data/libx11-protocol-perl-0.56/eg/widgets.c:375:5:  [4] (format) sprintf:
  Potential format string problem (CWE-134). Make format string constant.
    sprintf(buf, fontname, fontsize);
data/libx11-protocol-perl-0.56/eg/widgets.c:581:3:  [4] (format) sprintf:
  Potential format string problem (CWE-134). Make format string constant.
		sprintf(buf, fontname, fontsize);
data/libx11-protocol-perl-0.56/eg/widgets.c:113: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 buf[256];
data/libx11-protocol-perl-0.56/eg/widgets.c:269: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[5]; /* 1 0 0 % \0 */
data/libx11-protocol-perl-0.56/eg/widgets.c:273:5:  [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(str, "%d%%", (int)(frac * 100.0));

ANALYSIS SUMMARY:

Hits = 5
Lines analyzed = 739 in approximately 0.03 seconds (21761 lines/second)
Physical Source Lines of Code (SLOC) = 580
Hits@level = [0]   0 [1]   0 [2]   3 [3]   0 [4]   2 [5]   0
Hits@level+ = [0+]   5 [1+]   5 [2+]   5 [3+]   2 [4+]   2 [5+]   0
Hits/KSLOC@level+ = [0+] 8.62069 [1+] 8.62069 [2+] 8.62069 [3+] 3.44828 [4+] 3.44828 [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.