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/lzd-1.1/lzd.cc

FINAL RESULTS:

data/lzd-1.1/lzd.cc:151:36:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  uint8_t get_byte() { return std::getc( stdin ); }
data/lzd-1.1/lzd.cc:431:51:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    for( int i = 0; i < 6; ++i ) header[i] = std::getc( stdin );
data/lzd-1.1/lzd.cc:450:53:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    for( int i = 0; i < 20; ++i ) trailer[i] = std::getc( stdin );

ANALYSIS SUMMARY:

Hits = 3
Lines analyzed = 463 in approximately 0.04 seconds (12193 lines/second)
Physical Source Lines of Code (SLOC) = 384
Hits@level = [0]   5 [1]   3 [2]   0 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   8 [1+]   3 [2+]   0 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 20.8333 [1+] 7.8125 [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.