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/abicheck-1.2/test/libc_a.c
Examining data/abicheck-1.2/test/private1.c
Examining data/abicheck-1.2/test/public1.c

FINAL RESULTS:

data/abicheck-1.2/test/public1.c:17:11:  [2] (misc) open:
  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).
	int fd = open("/dev/null", O_WRONLY);
data/abicheck-1.2/test/private1.c:33:7:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	if ( strlen(str) == 2 ) {

ANALYSIS SUMMARY:

Hits = 2
Lines analyzed = 78 in approximately 0.01 seconds (7744 lines/second)
Physical Source Lines of Code (SLOC) = 45
Hits@level = [0]   4 [1]   1 [2]   1 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   6 [1+]   2 [2+]   1 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 133.333 [1+] 44.4444 [2+] 22.2222 [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.