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/libcsv-3.0.3+dfsg/csv.h
Examining data/libcsv-3.0.3+dfsg/examples/csvfix.c
Examining data/libcsv-3.0.3+dfsg/examples/csvinfo.c
Examining data/libcsv-3.0.3+dfsg/examples/csvtest.c
Examining data/libcsv-3.0.3+dfsg/examples/csvvalid.c
Examining data/libcsv-3.0.3+dfsg/libcsv.c
Examining data/libcsv-3.0.3+dfsg/test_csv.c

FINAL RESULTS:

data/libcsv-3.0.3+dfsg/examples/csvfix.c:23: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[1024];
data/libcsv-3.0.3+dfsg/examples/csvfix.c:39:12:  [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).
  infile = fopen(argv[1], "rb");
data/libcsv-3.0.3+dfsg/examples/csvfix.c:45:13:  [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).
  outfile = fopen(argv[2], "wb");
data/libcsv-3.0.3+dfsg/examples/csvinfo.c:36: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[1024];
data/libcsv-3.0.3+dfsg/examples/csvinfo.c:61:10:  [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(*argv, "rb");
data/libcsv-3.0.3+dfsg/examples/csvvalid.c:18: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[1024];
data/libcsv-3.0.3+dfsg/examples/csvvalid.c:35:10:  [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(argv[i], "rb");
data/libcsv-3.0.3+dfsg/examples/csvtest.c:34:13:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  while ((i=getc(stdin)) != EOF) {

ANALYSIS SUMMARY:

Hits = 8
Lines analyzed = 1425 in approximately 0.08 seconds (18772 lines/second)
Physical Source Lines of Code (SLOC) = 1070
Hits@level = [0]  26 [1]   1 [2]   7 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  34 [1+]   8 [2+]   7 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 31.7757 [1+] 7.47664 [2+] 6.54206 [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.