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/darts-0.32/acconfig.h
Examining data/darts-0.32/mkdarts.cpp
Examining data/darts-0.32/darts.h
Examining data/darts-0.32/darts.cpp

FINAL RESULTS:

data/darts-0.32/mkdarts.cpp:65:10:  [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).
    std::strcpy(tmp, line.c_str());
data/darts-0.32/darts.cpp:22:10:  [2] (misc) open:
  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).
  if (da.open(index.c_str())) {
data/darts-0.32/darts.h:144:9:  [2] (misc) open:
  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).
    int open(const char *file,
data/darts-0.32/darts.h:148:28:  [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).
      std::FILE *fp = std::fopen(file, mode);
data/darts-0.32/darts.h:174:28:  [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).
      std::FILE *fp = std::fopen(file, mode);
data/darts-0.32/darts.h:188:29:  [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).
      std::FILE *fp  = std::fopen(file, mode);
data/darts-0.32/darts.h:195:11:  [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[8];
data/darts-0.32/darts.h:43:19:  [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).
    { return std::strlen(key); }

ANALYSIS SUMMARY:

Hits = 8
Lines analyzed = 652 in approximately 0.04 seconds (16143 lines/second)
Physical Source Lines of Code (SLOC) = 503
Hits@level = [0]   5 [1]   1 [2]   6 [3]   0 [4]   1 [5]   0
Hits@level+ = [0+]  13 [1+]   8 [2+]   7 [3+]   1 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 25.8449 [1+] 15.9046 [2+] 13.9165 [3+] 1.98807 [4+] 1.98807 [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.