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-criterion-measurement-0.1.2.0/cbits/cycles.c
Examining data/haskell-criterion-measurement-0.1.2.0/cbits/time-osx.c
Examining data/haskell-criterion-measurement-0.1.2.0/cbits/time-posix.c
Examining data/haskell-criterion-measurement-0.1.2.0/cbits/time-windows.c

FINAL RESULTS:

data/haskell-criterion-measurement-0.1.2.0/cbits/cycles.c:48:7:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  if (read (fddev, &result, sizeof(result)) < sizeof(result))

ANALYSIS SUMMARY:

Hits = 1
Lines analyzed = 196 in approximately 0.02 seconds (8735 lines/second)
Physical Source Lines of Code (SLOC) = 133
Hits@level = [0]   0 [1]   1 [2]   0 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   1 [1+]   1 [2+]   0 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 7.5188 [1+] 7.5188 [2+]   0 [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.