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/treil-1.8/heap.h
Examining data/treil-1.8/ruby/treil.c
Examining data/treil-1.8/tree.c
Examining data/treil-1.8/treil.h
Examining data/treil-1.8/heap.c
Examining data/treil-1.8/rect.c

FINAL RESULTS:

data/treil-1.8/tree.c:130:3:  [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.
  char buf[BUFSIZ];
data/treil-1.8/tree.c:149:21:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
      ssize_t len = read (fd, buf, BUFSIZ);

ANALYSIS SUMMARY:

Hits = 2
Lines analyzed = 751 in approximately 0.06 seconds (12491 lines/second)
Physical Source Lines of Code (SLOC) = 564
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+] 3.5461 [1+] 3.5461 [2+] 1.77305 [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.