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/haskell-hashable-1.3.0.0/benchmarks/cbits/inthash.c
Examining data/haskell-hashable-1.3.0.0/benchmarks/cbits/siphash-sse2.c
Examining data/haskell-hashable-1.3.0.0/benchmarks/cbits/siphash-sse41.c
Examining data/haskell-hashable-1.3.0.0/benchmarks/cbits/siphash.c
Examining data/haskell-hashable-1.3.0.0/benchmarks/cbits/wang.c
Examining data/haskell-hashable-1.3.0.0/cbits/fnv.c
Examining data/haskell-hashable-1.3.0.0/cbits/getRandomBytes.c
Examining data/haskell-hashable-1.3.0.0/cbits/mmap.c

FINAL RESULTS:

data/haskell-hashable-1.3.0.0/benchmarks/cbits/siphash-sse41.c:27:11:  [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.
	unsigned char key[16];
data/haskell-hashable-1.3.0.0/cbits/getRandomBytes.c:74:8:  [2] (misc) open:
  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).
  fd = open("/dev/urandom", O_RDONLY);
data/haskell-hashable-1.3.0.0/cbits/getRandomBytes.c:79:13:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    nread = read(fd, dest + off, nbytes);

ANALYSIS SUMMARY:

Hits = 3
Lines analyzed = 721 in approximately 0.05 seconds (13178 lines/second)
Physical Source Lines of Code (SLOC) = 463
Hits@level = [0]   0 [1]   1 [2]   2 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   3 [1+]   3 [2+]   2 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 6.47948 [1+] 6.47948 [2+] 4.31965 [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.