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/octave-io-2.6.3/src/csvconcat.cc
Examining data/octave-io-2.6.3/src/num2col.cc
Examining data/octave-io-2.6.3/src/col2num.cc
Examining data/octave-io-2.6.3/src/cell2csv.cc
Examining data/octave-io-2.6.3/src/csvexplode.cc
Examining data/octave-io-2.6.3/src/csv2cell.cc
Examining data/octave-io-2.6.3/src/octave_4_2_compatibility.h

FINAL RESULTS:

data/octave-io-2.6.3/src/cell2csv.cc:119:9:  [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 tmp[30];
data/octave-io-2.6.3/src/cell2csv.cc:120:9:  [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(tmp, "%.15g", c(i, j).double_value());
data/octave-io-2.6.3/src/csv2cell.cc:362: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 line [MAXSTRINGLENGTH];
data/octave-io-2.6.3/src/csvconcat.cc:69:2:  [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 tmp[20];
data/octave-io-2.6.3/src/csvconcat.cc:70:2:  [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(tmp, "%g", c(i, j).double_value());

ANALYSIS SUMMARY:

Hits = 5
Lines analyzed = 1026 in approximately 0.06 seconds (18647 lines/second)
Physical Source Lines of Code (SLOC) = 497
Hits@level = [0]   0 [1]   0 [2]   5 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   5 [1+]   5 [2+]   5 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 10.0604 [1+] 10.0604 [2+] 10.0604 [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.