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/maxima-sage-5.44.0/interfaces/xmaxima/win32/winkill.c
Examining data/maxima-sage-5.44.0/interfaces/xmaxima/win32/winkill_lib.c
Examining data/maxima-sage-5.44.0/crosscompile-windows/maxima_longnames.c

FINAL RESULTS:

data/maxima-sage-5.44.0/interfaces/xmaxima/win32/winkill.c:165:3:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
  fprintf(stderr,s);
data/maxima-sage-5.44.0/crosscompile-windows/maxima_longnames.c:19:5:  [2] (buffer) TCHAR:
  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.
    TCHAR  buffer[BUFSIZE];
data/maxima-sage-5.44.0/interfaces/xmaxima/win32/winkill.c:50:3:  [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 name[20] ;
data/maxima-sage-5.44.0/interfaces/xmaxima/win32/winkill.c:228:3:  [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(sharedMemory.name,"gcl-%d", pid);
data/maxima-sage-5.44.0/interfaces/xmaxima/win32/winkill.c:236: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(sharedMemory.name,"maxima-%d", pid);
data/maxima-sage-5.44.0/interfaces/xmaxima/win32/winkill_lib.c:38:3:  [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 name[20] ;
data/maxima-sage-5.44.0/interfaces/xmaxima/win32/winkill_lib.c:177: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 ( sharedMemory.name, "maxima-%d", getpid());

ANALYSIS SUMMARY:

Hits = 7
Lines analyzed = 596 in approximately 0.14 seconds (4140 lines/second)
Physical Source Lines of Code (SLOC) = 447
Hits@level = [0]  12 [1]   0 [2]   6 [3]   0 [4]   1 [5]   0
Hits@level+ = [0+]  19 [1+]   7 [2+]   7 [3+]   1 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 42.5056 [1+] 15.66 [2+] 15.66 [3+] 2.23714 [4+] 2.23714 [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.