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/libpj-java-0.0~20150107+dfsg/lib/edu/rit/clu/monte/doc-files/Random.c
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/clu/monte/doc-files/PiClu.c
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/clu/monte/doc-files/PiSeq.c
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/clu/monte/doc-files/Random.h
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/clu/network/doc-files/FloydSeq.c
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/clu/network/doc-files/FloydClu.c
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/monte/doc-files/Random.c
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/monte/doc-files/Random.h
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/monte/doc-files/PiSeq3.c
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/monte/doc-files/PiSmp3.c
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/network/doc-files/FloydSeq.c
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/network/doc-files/FloydSmpRow.c
Examining data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/network/doc-files/FloydSmpGuided.c

FINAL RESULTS:

data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/network/doc-files/FloydSeq.c:180: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).
		in = fopen (infile, "r");
data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/network/doc-files/FloydSeq.c:220:9:  [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).
		out = fopen (outfile, "w");
data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/network/doc-files/FloydSmpGuided.c:191: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).
		in = fopen (infile, "r");
data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/network/doc-files/FloydSmpGuided.c:247:9:  [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).
		out = fopen (outfile, "w");
data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/network/doc-files/FloydSmpRow.c:191: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).
		in = fopen (infile, "r");
data/libpj-java-0.0~20150107+dfsg/lib/edu/rit/smp/network/doc-files/FloydSmpRow.c:247:9:  [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).
		out = fopen (outfile, "w");

ANALYSIS SUMMARY:

Hits = 6
Lines analyzed = 2299 in approximately 0.54 seconds (4228 lines/second)
Physical Source Lines of Code (SLOC) = 1047
Hits@level = [0]  92 [1]   0 [2]   6 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  98 [1+]   6 [2+]   6 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 93.6008 [1+] 5.73066 [2+] 5.73066 [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.