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/gnucap-python-0.0.2/test_python.cc
Examining data/gnucap-python-0.0.2/c_python.cc
Examining data/gnucap-python-0.0.2/gnucap/s_tr_set.cc
Examining data/gnucap-python-0.0.2/gnucap/command.cc
Examining data/gnucap-python-0.0.2/gnucap/c_genrat.cc
Examining data/gnucap-python-0.0.2/gnucap/s_tr.cc
Examining data/gnucap-python-0.0.2/gnucap/s__out.cc
Examining data/gnucap-python-0.0.2/gnucap/s__solve.cc
Examining data/gnucap-python-0.0.2/gnucap/s__init.cc
Examining data/gnucap-python-0.0.2/gnucap/garbage.cc
Examining data/gnucap-python-0.0.2/gnucap/m_wave_.h
Examining data/gnucap-python-0.0.2/gnucap/s_tr_swp.cc
Examining data/gnucap-python-0.0.2/gnucap/wrap.h
Examining data/gnucap-python-0.0.2/misc/d_coil.cc
Examining data/gnucap-python-0.0.2/misc/d_brl.cc

FINAL RESULTS:

data/gnucap-python-0.0.2/c_python.cc:27:8:  [2] (misc) fopen:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  fp = fopen(file_name.c_str(), "r");
data/gnucap-python-0.0.2/gnucap/s__out.cc:95: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 format[20];
data/gnucap-python-0.0.2/gnucap/s__out.cc:97: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(format, "%%c%%-%us", width);
data/gnucap-python-0.0.2/test_python.cc:16:8:  [2] (misc) fopen:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  fp = fopen(file_name.c_str(), "r");

ANALYSIS SUMMARY:

Hits = 4
Lines analyzed = 2462 in approximately 0.77 seconds (3189 lines/second)
Physical Source Lines of Code (SLOC) = 1786
Hits@level = [0]   0 [1]   0 [2]   4 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   4 [1+]   4 [2+]   4 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 2.23964 [1+] 2.23964 [2+] 2.23964 [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.