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/jcifs-1.3.19/examples/pipes/callnp.c
Examining data/jcifs-1.3.19/examples/pipes/createnp.c
Examining data/jcifs-1.3.19/examples/pipes/createf.c

FINAL RESULTS:

data/jcifs-1.3.19/examples/pipes/callnp.c:88:30:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
                bufferSize = atoi(argv[i]);
data/jcifs-1.3.19/examples/pipes/createnp.c:110:30:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
                bufferSize = atoi(argv[i]);

ANALYSIS SUMMARY:

Hits = 2
Lines analyzed = 495 in approximately 0.25 seconds (1990 lines/second)
Physical Source Lines of Code (SLOC) = 386
Hits@level = [0] 123 [1]   0 [2]   2 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+] 125 [1+]   2 [2+]   2 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 323.834 [1+] 5.18135 [2+] 5.18135 [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.