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-bit64-4.0.5/src/integer64.h Examining data/r-cran-bit64-4.0.5/src/sort64.h Examining data/r-cran-bit64-4.0.5/src/bsearch.c Examining data/r-cran-bit64-4.0.5/src/init.c Examining data/r-cran-bit64-4.0.5/src/bsearch.h Examining data/r-cran-bit64-4.0.5/src/sortuse64.c Examining data/r-cran-bit64-4.0.5/src/hash64.c Examining data/r-cran-bit64-4.0.5/src/sort64.c Examining data/r-cran-bit64-4.0.5/src/integer64.c Examining data/r-cran-bit64-4.0.5/src/cache.c FINAL RESULTS: data/r-cran-bit64-4.0.5/src/integer64.c:191:4: [4] (format) snprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. snprintf(buff, NCHARS_DECS_INTEGER64, COERCE_INTEGER64, x[i]); data/r-cran-bit64-4.0.5/src/integer64.c:186:10: [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 buff[NCHARS_DECS_INTEGER64]; data/r-cran-bit64-4.0.5/src/integer64.c:217:10: [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 buff[NCHARS_BITS_INTEGER64]; data/r-cran-bit64-4.0.5/src/integer64.c:247:9: [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). l = strlen(str); ANALYSIS SUMMARY: Hits = 4 Lines analyzed = 7750 in approximately 0.19 seconds (40144 lines/second) Physical Source Lines of Code (SLOC) = 6479 Hits@level = [0] 0 [1] 1 [2] 2 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 4 [1+] 4 [2+] 3 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 0.617379 [1+] 0.617379 [2+] 0.463034 [3+] 0.154345 [4+] 0.154345 [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.