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/eweouz-0.12/src/eweouz-dump-addressbook.c
Examining data/eweouz-0.12/src/eweouz-write-addressbook.c

FINAL RESULTS:

data/eweouz-0.12/src/eweouz-write-addressbook.c:90: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[1024];
data/eweouz-0.12/src/eweouz-write-addressbook.c:94:16:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
			while ((r = read(0, buf, 1023)) > 0) {

ANALYSIS SUMMARY:

Hits = 2
Lines analyzed = 327 in approximately 0.03 seconds (10348 lines/second)
Physical Source Lines of Code (SLOC) = 236
Hits@level = [0]  17 [1]   1 [2]   1 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  19 [1+]   2 [2+]   1 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 80.5085 [1+] 8.47458 [2+] 4.23729 [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.