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/r-cran-deldir-0.2-3/src/init.c
Examining data/r-cran-deldir-0.2-3/inst/code.discarded/init.c
Examining data/r-cran-deldir-0.2-3/inst/code.discarded/trigraf.c
Examining data/r-cran-deldir-0.2-3/inst/code.discarded/fexitc.c

FINAL RESULTS:

data/r-cran-deldir-0.2-3/inst/code.discarded/fexitc.c:6: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 buf[256];
data/r-cran-deldir-0.2-3/inst/code.discarded/fexitc.c:11:5:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
    strncpy(buf, msg, nc);

ANALYSIS SUMMARY:

Hits = 2
Lines analyzed = 256 in approximately 0.02 seconds (12794 lines/second)
Physical Source Lines of Code (SLOC) = 168
Hits@level = [0]   0 [1]   1 [2]   1 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   2 [1+]   2 [2+]   1 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 11.9048 [1+] 11.9048 [2+] 5.95238 [3+]   0 [4+]   0 [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.