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/pd-libdir-1.11/libdir.c

FINAL RESULTS:

data/pd-libdir-1.11/libdir.c:125:7:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination
  [MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
  snprintf (warning: strncat is easily misused).
      strcat(helppathname, classname);
data/pd-libdir-1.11/libdir.c:65:9:  [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 encoded[MAXPDSTRING];
data/pd-libdir-1.11/libdir.c:99:5:  [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 fullclassname[FILENAME_MAX], dirbuf[FILENAME_MAX];
data/pd-libdir-1.11/libdir.c:121:7:  [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 helppathname[FILENAME_MAX];
data/pd-libdir-1.11/libdir.c:124:7:  [2] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination
  [MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
  snprintf (warning: strncat is easily misused). Risk is low because the
  source is a constant string.
      strcat(helppathname, "/doc/5.reference/");
data/pd-libdir-1.11/libdir.c:142:5:  [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 fullclassname[FILENAME_MAX], dirbuf[FILENAME_MAX];
data/pd-libdir-1.11/libdir.c:122:7:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
      strncpy(helppathname, sys_libdir->s_name, FILENAME_MAX-30);

ANALYSIS SUMMARY:

Hits = 7
Lines analyzed = 194 in approximately 0.01 seconds (13267 lines/second)
Physical Source Lines of Code (SLOC) = 142
Hits@level = [0]   1 [1]   1 [2]   5 [3]   0 [4]   1 [5]   0
Hits@level+ = [0+]   8 [1+]   7 [2+]   6 [3+]   1 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 56.338 [1+] 49.2958 [2+] 42.2535 [3+] 7.04225 [4+] 7.04225 [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.