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/wmcalclock-1.25/Src/wmCalClock.c
Examining data/wmcalclock-1.25/Src/xutils.c
Examining data/wmcalclock-1.25/Src/xutils.h

FINAL RESULTS:

data/wmcalclock-1.25/Src/wmCalClock.c:812:13:  [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(TimeColor, argv[++i]);
data/wmcalclock-1.25/Src/wmCalClock.c:821:13:  [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(BackgroundColor, argv[++i]);
data/wmcalclock-1.25/Src/wmCalClock.c:854:6:  [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(ExecuteCommand, argv[++i]);
data/wmcalclock-1.25/Src/wmCalClock.c:1034:9:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
        sprintf(Command, "%s &", ExecuteCommand);
data/wmcalclock-1.25/Src/wmCalClock.c:1035:9:  [4] (shell) system:
  This causes a new program to execute and is difficult to use safely
  (CWE-78). try using a library call that implements the same functionality
  if available.
        system(Command);
data/wmcalclock-1.25/Src/wmCalClock.c:281: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	ExecuteCommand[1024];
data/wmcalclock-1.25/Src/wmCalClock.c:284: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    TimeColor[30]    	= "#ffff00";
data/wmcalclock-1.25/Src/wmCalClock.c:285: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    BackgroundColor[30]    	= "#181818";
data/wmcalclock-1.25/Src/wmCalClock.c:845:15:  [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).
	    Volume = atoi(argv[++i]);
data/wmcalclock-1.25/Src/wmCalClock.c:1011: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 Command[512];
data/wmcalclock-1.25/Src/xutils.c:65:8:  [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.
extern char    TimeColor[30];
data/wmcalclock-1.25/Src/xutils.c:66:8:  [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.
extern char    BackgroundColor[30];
data/wmcalclock-1.25/Src/wmCalClock.c:751:4:  [1] (obsolete) usleep:
  This C routine is considered obsolete (as opposed to the shell command by
  the same name). The interaction of this function with SIGALRM and other
  timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
  unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
	  usleep(DELAY);
data/wmcalclock-1.25/Src/wmCalClock.c:753:4:  [1] (obsolete) usleep:
  This C routine is considered obsolete (as opposed to the shell command by
  the same name). The interaction of this function with SIGALRM and other
  timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
  unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
	  usleep( 200000L);
data/wmcalclock-1.25/Src/wmCalClock.c:755:4:  [1] (obsolete) usleep:
  This C routine is considered obsolete (as opposed to the shell command by
  the same name). The interaction of this function with SIGALRM and other
  timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
  unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
	  usleep( 500000L);

ANALYSIS SUMMARY:

Hits = 15
Lines analyzed = 1468 in approximately 0.06 seconds (24748 lines/second)
Physical Source Lines of Code (SLOC) = 765
Hits@level = [0]  32 [1]   3 [2]   7 [3]   0 [4]   5 [5]   0
Hits@level+ = [0+]  47 [1+]  15 [2+]  12 [3+]   5 [4+]   5 [5+]   0
Hits/KSLOC@level+ = [0+] 61.4379 [1+] 19.6078 [2+] 15.6863 [3+] 6.53595 [4+] 6.53595 [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.