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/gkrellm-x86info-0.0.2/MHz.c
Examining data/gkrellm-x86info-0.0.2/gkx86info.c
Examining data/gkrellm-x86info-0.0.2/gkx86info.h

FINAL RESULTS:

data/gkrellm-x86info-0.0.2/MHz.c:49:2:  [2] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf. Risk is low because the source has a constant maximum length.
	sprintf(buffer, "%lldMHz",
data/gkrellm-x86info-0.0.2/MHz.c:41:2:  [1] (obsolete) usleep:
  This C routine is considered obsolete (as opposed to the shell command by
  the same name). The interaction of this function with SIGALRM and other
  timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
  unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
	usleep(100);

ANALYSIS SUMMARY:

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