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-gam-1.20/src/gam_init.c Examining data/r-cran-gam-1.20/src/modreg.h Examining data/r-cran-gam-1.20/src/sbart.c Examining data/r-cran-gam-1.20/src/loessc.c FINAL RESULTS: data/r-cran-gam-1.20/src/loessc.c:768:2: [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(mess,num); data/r-cran-gam-1.20/src/loessc.c:799:2: [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(mess,num); data/r-cran-gam-1.20/src/loessc.c:657: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 *msg, msg2[100]; data/r-cran-gam-1.20/src/loessc.c:737:11: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. default: sprintf(msg=msg2,"Assert failed; error code %d\n",*i); data/r-cran-gam-1.20/src/loessc.c:756: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 mess[4000], num[20]; data/r-cran-gam-1.20/src/loessc.c:766:2: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(num," %d",i[j * *inc]); data/r-cran-gam-1.20/src/loessc.c:787: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 mess[4000], num[30]; data/r-cran-gam-1.20/src/loessc.c:797:2: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(num," %.5g",x[j * *inc]); data/r-cran-gam-1.20/src/loessc.c:760:5: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(mess,s,*nc); data/r-cran-gam-1.20/src/loessc.c:772:5: [1] (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 character. strcat(mess,"\n"); data/r-cran-gam-1.20/src/loessc.c:791:5: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(mess,s,*nc); data/r-cran-gam-1.20/src/loessc.c:803:5: [1] (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 character. strcat(mess,"\n"); ANALYSIS SUMMARY: Hits = 12 Lines analyzed = 2070 in approximately 0.07 seconds (29998 lines/second) Physical Source Lines of Code (SLOC) = 853 Hits@level = [0] 0 [1] 4 [2] 6 [3] 0 [4] 2 [5] 0 Hits@level+ = [0+] 12 [1+] 12 [2+] 8 [3+] 2 [4+] 2 [5+] 0 Hits/KSLOC@level+ = [0+] 14.068 [1+] 14.068 [2+] 9.37866 [3+] 2.34467 [4+] 2.34467 [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.