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/naspro-core-0.5.1/include/NASPRO/core/list.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/sem.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/locale.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/string.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/cc.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/lib.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/dl.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/types.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/thread.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/msg.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/avl.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/env.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/fs.h
Examining data/naspro-core-0.5.1/include/NASPRO/core/mutex.h
Examining data/naspro-core-0.5.1/src/avl.c
Examining data/naspro-core-0.5.1/src/localepvt.h
Examining data/naspro-core-0.5.1/src/msg.c
Examining data/naspro-core-0.5.1/src/string.c
Examining data/naspro-core-0.5.1/src/internal.h
Examining data/naspro-core-0.5.1/src/win32/locale.c
Examining data/naspro-core-0.5.1/src/win32/fs.c
Examining data/naspro-core-0.5.1/src/win32/mutex.c
Examining data/naspro-core-0.5.1/src/win32/sem.c
Examining data/naspro-core-0.5.1/src/win32/env.c
Examining data/naspro-core-0.5.1/src/win32/thread.c
Examining data/naspro-core-0.5.1/src/win32/dl.c
Examining data/naspro-core-0.5.1/src/types.c
Examining data/naspro-core-0.5.1/src/list.c
Examining data/naspro-core-0.5.1/src/posix/locale.c
Examining data/naspro-core-0.5.1/src/posix/mutex.c
Examining data/naspro-core-0.5.1/src/posix/sem.c
Examining data/naspro-core-0.5.1/src/posix/env.c
Examining data/naspro-core-0.5.1/src/posix/thread.c
Examining data/naspro-core-0.5.1/src/posix/dl.c
Examining data/naspro-core-0.5.1/src/posix/fs.c

FINAL RESULTS:

data/naspro-core-0.5.1/include/NASPRO/core/cc.h:170:24:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	__attribute__((format(printf, string_index, first_to_check)))
data/naspro-core-0.5.1/src/posix/locale.c:70:2:  [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(buf, sep);
data/naspro-core-0.5.1/src/win32/locale.c:158:2:  [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(buf, lconv->decimal_point);
data/naspro-core-0.5.1/src/posix/env.c:17:8:  [3] (buffer) getenv:
  Environment variables are untrustable input if they can be set by an
  attacker. They can have any content and length, and the same variable can
  be set more than once (CWE-807, CWE-20). Check environment variables
  carefully before using them.
	ret = getenv(name);
data/naspro-core-0.5.1/src/win32/mutex.c:34:2:  [3] (misc) InitializeCriticalSection:
  Exceptions can be thrown in low-memory situations. Use
  InitializeCriticalSectionAndSpinCount instead.
	InitializeCriticalSection(&ret->cs);
data/naspro-core-0.5.1/src/win32/mutex.c:57:3:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead.
		EnterCriticalSection(&mutex->cs);
data/naspro-core-0.5.1/src/avl.c:327:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(ret->value, value, size);
data/naspro-core-0.5.1/src/avl.c:779:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(new_val, value, size);
data/naspro-core-0.5.1/src/list.c:111:2:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	memcpy(ret->value, value, size);
data/naspro-core-0.5.1/src/list.c:575:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(new_val, value, size);
data/naspro-core-0.5.1/src/string.c:306:2:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	memcpy(ret, s, len);
data/naspro-core-0.5.1/src/string.c:1903:2:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	memcpy(str, v, ret);
data/naspro-core-0.5.1/src/string.c:2022:2:  [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 dec_sep[dec_sep_len + 1];
data/naspro-core-0.5.1/src/string.c:2041:2:  [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 dec_sep[dec_sep_len + 1];
data/naspro-core-0.5.1/src/string.c:2093:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(buf, s, s_len);
data/naspro-core-0.5.1/src/win32/env.c:20: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.
	const char buf[32767 * 2];
data/naspro-core-0.5.1/src/posix/locale.c:52:30:  [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).
	return (*ret == '\0') ? 1 : strlen(ret);
data/naspro-core-0.5.1/src/string.c:281: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).
	return strlen(s) + 1;
data/naspro-core-0.5.1/src/string.c:302:8:  [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).
	len = strlen(s) + 1;
data/naspro-core-0.5.1/src/string.c:1129:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(str, E ? "NAN" : "nan", 3);
data/naspro-core-0.5.1/src/string.c:1134:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(str, E ? "INF" : "inf", 3);
data/naspro-core-0.5.1/src/string.c:1144:4:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
			strncpy(str, dec_sep, dec_sep_len);
data/naspro-core-0.5.1/src/string.c:1154:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(str, E ? "E+00" : "e+00", 4);
data/naspro-core-0.5.1/src/string.c:1171:4:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
			strncpy(str, dec_sep, dec_sep_len);
data/naspro-core-0.5.1/src/string.c:1300:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(str, F ? "NAN" : "nan", 3);
data/naspro-core-0.5.1/src/string.c:1305:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(str, F ? "INF" : "inf", 3);
data/naspro-core-0.5.1/src/string.c:1331:4:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
			strncpy(str, dec_sep, dec_sep_len);
data/naspro-core-0.5.1/src/string.c:1517:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(str, G ? "NAN" : "nan", 3);
data/naspro-core-0.5.1/src/string.c:1522:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(str, G ? "INF" : "inf", 3);
data/naspro-core-0.5.1/src/string.c:1546:5:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
				strncpy(str, dec_sep, dec_sep_len);
data/naspro-core-0.5.1/src/string.c:1614:5:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
				strncpy(str, dec_sep, dec_sep_len);
data/naspro-core-0.5.1/src/string.c:1762:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(str, A ? "NAN" : "nan", 3);
data/naspro-core-0.5.1/src/string.c:1767:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(str, A ? "INF" : "inf", 3);
data/naspro-core-0.5.1/src/string.c:1790:4:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
			strncpy(str, dec_sep, dec_sep_len);
data/naspro-core-0.5.1/src/string.c:1806:4:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
			strncpy(str, dec_sep, dec_sep_len);
data/naspro-core-0.5.1/src/string.c:1896:10:  [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).
				   : strlen(v);
data/naspro-core-0.5.1/src/string.c:2078:43:  [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).
	for (buf = NULL, buf_size = 0, sep_len = strlen(sep),
data/naspro-core-0.5.1/src/win32/locale.c:150: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).
	return strlen(lconv->decimal_point);

ANALYSIS SUMMARY:

Hits = 38
Lines analyzed = 8836 in approximately 0.18 seconds (47773 lines/second)
Physical Source Lines of Code (SLOC) = 4634
Hits@level = [0]  10 [1]  22 [2]  10 [3]   3 [4]   3 [5]   0
Hits@level+ = [0+]  48 [1+]  38 [2+]  16 [3+]   6 [4+]   3 [5+]   0
Hits/KSLOC@level+ = [0+] 10.3582 [1+] 8.20026 [2+] 3.45274 [3+] 1.29478 [4+] 0.647389 [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.