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/shhopt-1.1.7/shhopt.h
Examining data/shhopt-1.1.7/shhopt.c
Examining data/shhopt-1.1.7/example.c

FINAL RESULTS:

data/shhopt-1.1.7/shhopt.c:55:5:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
    vfprintf(stderr, format, ap);
data/shhopt-1.1.7/shhopt.c:138:12:  [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.
    static char ret[31];
data/shhopt-1.1.7/shhopt.c:141:2:  [2] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused). Risk is low because the source is a constant string.
	strcpy(ret, "--");
data/shhopt-1.1.7/shhopt.c:107:17:  [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).
	    matchlen = strlen(s);
data/shhopt-1.1.7/shhopt.c:142:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy(ret + 2, opt->longName, 28);

ANALYSIS SUMMARY:

Hits = 5
Lines analyzed = 610 in approximately 0.03 seconds (22734 lines/second)
Physical Source Lines of Code (SLOC) = 351
Hits@level = [0]  11 [1]   2 [2]   2 [3]   0 [4]   1 [5]   0
Hits@level+ = [0+]  16 [1+]   5 [2+]   3 [3+]   1 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 45.584 [1+] 14.245 [2+] 8.54701 [3+] 2.849 [4+] 2.849 [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.