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/codegroup-19981025/codegroup.c

FINAL RESULTS:

data/codegroup-19981025/codegroup.c:165:5:  [4] (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).
    strcpy(linebuf + linelen, groupbuf);
data/codegroup-19981025/codegroup.c:46:8:  [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 groupbuf[GROUPLEN + 1];   /* Group assembly buffer */
data/codegroup-19981025/codegroup.c:47:8:  [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 linebuf[LINELEN + 4];     /* Line editing buffer */
data/codegroup-19981025/codegroup.c:220:5:  [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(groupbuf, "ZZZZZ");        /* Place start sentinel */
data/codegroup-19981025/codegroup.c:247:5:  [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(groupbuf, "WWWWW");        /* Place end sentinel */
data/codegroup-19981025/codegroup.c:643:35:  [2] (misc) fopen:
  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).
                        if ((fi = fopen(cp, "r")) == NULL) {
data/codegroup-19981025/codegroup.c:653:35:  [2] (misc) fopen:
  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).
                        if ((fo = fopen(cp, "w")) == NULL) {

ANALYSIS SUMMARY:

Hits = 7
Lines analyzed = 681 in approximately 0.06 seconds (10721 lines/second)
Physical Source Lines of Code (SLOC) = 520
Hits@level = [0]  20 [1]   0 [2]   6 [3]   0 [4]   1 [5]   0
Hits@level+ = [0+]  27 [1+]   7 [2+]   7 [3+]   1 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 51.9231 [1+] 13.4615 [2+] 13.4615 [3+] 1.92308 [4+] 1.92308 [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.