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/libdisorder-0.0.2+git20130809.8062ee1/code/include/disorder.h
Examining data/libdisorder-0.0.2+git20130809.8062ee1/code/src/disorder.c
Examining data/libdisorder-0.0.2+git20130809.8062ee1/code/test/test.c
Examining data/libdisorder-0.0.2+git20130809.8062ee1/code/tool/ropy.c

FINAL RESULTS:

data/libdisorder-0.0.2+git20130809.8062ee1/code/test/test.c:50: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).
  fin = fopen("/dev/urandom","r");
data/libdisorder-0.0.2+git20130809.8062ee1/code/tool/ropy.c:91: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).
  fin = fopen(filename, "r");
data/libdisorder-0.0.2+git20130809.8062ee1/code/test/test.c:69:11:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
      x = fgetc(fin);
data/libdisorder-0.0.2+git20130809.8062ee1/code/tool/ropy.c:123:17:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  while(EOF!=(x=fgetc(fin)))

ANALYSIS SUMMARY:

Hits = 4
Lines analyzed = 514 in approximately 0.02 seconds (22169 lines/second)
Physical Source Lines of Code (SLOC) = 287
Hits@level = [0]   6 [1]   2 [2]   2 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  10 [1+]   4 [2+]   2 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 34.8432 [1+] 13.9373 [2+] 6.96864 [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.