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/golang-github-golang-leveldb-0.0~git20161231.0.3435554/testdata/make-db.cc
Examining data/golang-github-golang-leveldb-0.0~git20161231.0.3435554/testdata/make-table.cc

FINAL RESULTS:

data/golang-github-golang-leveldb-0.0~git20161231.0.3435554/testdata/make-table.cc:66:5:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
int read() {
data/golang-github-golang-leveldb-0.0~git20161231.0.3435554/testdata/make-table.cc:110:10:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  return read();

ANALYSIS SUMMARY:

Hits = 2
Lines analyzed = 230 in approximately 0.04 seconds (5683 lines/second)
Physical Source Lines of Code (SLOC) = 166
Hits@level = [0]   0 [1]   2 [2]   0 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   2 [1+]   2 [2+]   0 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 12.0482 [1+] 12.0482 [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.