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-gi-gtk-hs-0.3.9/cbits/Gtk2HsStore.c Examining data/haskell-gi-gtk-hs-0.3.9/cbits/Gtk2HsStore.h Examining data/haskell-gi-gtk-hs-0.3.9/cbits/quartzfix.c FINAL RESULTS: data/haskell-gi-gtk-hs-0.3.9/cbits/Gtk2HsStore.c:287:18: [3] (random) g_random_int: This function is not sufficiently random for security-related functions such as key and nonce creation (CWE-327). Use a more secure technique for acquiring random values. store->stamp = g_random_int(); /* Random int to check whether an iter belongs to our model */ ANALYSIS SUMMARY: Hits = 1 Lines analyzed = 865 in approximately 0.06 seconds (14233 lines/second) Physical Source Lines of Code (SLOC) = 587 Hits@level = [0] 2 [1] 0 [2] 0 [3] 1 [4] 0 [5] 0 Hits@level+ = [0+] 3 [1+] 1 [2+] 1 [3+] 1 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 5.11073 [1+] 1.70358 [2+] 1.70358 [3+] 1.70358 [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.