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/holes-0.1/holes.c

FINAL RESULTS:

data/holes-0.1/holes.c:81:14:  [3] (buffer) getopt:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
	while ((c = getopt(argc, argv, "b:n:s")) != -1)
data/holes-0.1/holes.c:20:9:  [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.
	static char buf[16384];
data/holes-0.1/holes.c:123:16:  [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).
			    stdin : fopen(argv[i], "rb");

ANALYSIS SUMMARY:

Hits = 3
Lines analyzed = 140 in approximately 0.01 seconds (10892 lines/second)
Physical Source Lines of Code (SLOC) = 125
Hits@level = [0]  12 [1]   0 [2]   2 [3]   1 [4]   0 [5]   0
Hits@level+ = [0+]  15 [1+]   3 [2+]   3 [3+]   1 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 120 [1+]  24 [2+]  24 [3+]   8 [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.