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/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/dlgs.c
Examining data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/dlgs.h
Examining data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/example_client.c
Examining data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/main_wdgt.c
Examining data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/main_wdgt.h
Examining data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/python_bridge.c
Examining data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/python_bridge.h
Examining data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/python_stdout_stderr.c
Examining data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/python_stdout_stderr.h
Examining data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/review_wdgt.c
Examining data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/review_wdgt.h

FINAL RESULTS:

data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/example_client.c:41: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 result[256];
data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/python_bridge.c:76: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 filename[STR_SIZE+1];
data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/python_bridge.c:90: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 filename[STR_SIZE+1];
data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/python_bridge.c:666: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 buf[256];
data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/main_wdgt.c:44:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120). Risk is low because the source is a
  constant string.
  strncpy(filename, "example_path", str_size);
data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/main_wdgt.c:54:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120). Risk is low because the source is a
  constant string.
  strncpy(filename, "example_path", str_size);
data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/python_bridge.c:667:7:  [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).
  if (strlen(expression) + 26 > sizeof(buf))
data/mnemosyne-2.7.3+ds1/mnemosyne/embedded_in_C/python_bridge.c:682:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
  strncpy(result, PyString_AsString(obj), bufsize);

ANALYSIS SUMMARY:

Hits = 8
Lines analyzed = 1203 in approximately 0.06 seconds (20838 lines/second)
Physical Source Lines of Code (SLOC) = 837
Hits@level = [0]  48 [1]   4 [2]   4 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  56 [1+]   8 [2+]   4 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 66.9056 [1+] 9.55795 [2+] 4.77897 [3+]   0 [4+]   0 [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.