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/poe.app-0.5.1/vcedit.c
Examining data/poe.app-0.5.1/vcedit.h
Examining data/poe.app-0.5.1/OGGEditor.h
Examining data/poe.app-0.5.1/Document.h
Examining data/poe.app-0.5.1/Util.h
Examining data/poe.app-0.5.1/PreferencesWindowController.h
Examining data/poe.app-0.5.1/Controller.h
Examining data/poe.app-0.5.1/SwitchTableView.h
Examining data/poe.app-0.5.1/AddPanelController.h
Examining data/poe.app-0.5.1/EditorWindowController.h
Examining data/poe.app-0.5.1/NSMutableArray+goodies.h
Examining data/poe.app-0.5.1/ExtendedTableColumn.h

FINAL RESULTS:

data/poe.app-0.5.1/vcedit.c:291: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(state->vendor, state->vc->vendor);
data/poe.app-0.5.1/vcedit.c:113: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(op->packet, opb.buffer, oggpack_bytes(&opb));
data/poe.app-0.5.1/vcedit.c:245: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(state->mainbuf, header_main.packet, header_main.bytes);
data/poe.app-0.5.1/vcedit.c:270:7:  [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(state->bookbuf, header->packet, 
data/poe.app-0.5.1/vcedit.c:93:21:  [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).
	oggpack_write(&opb,strlen(vendor),32);
data/poe.app-0.5.1/vcedit.c:94: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).
	_v_writestring(&opb,vendor, strlen(vendor));
data/poe.app-0.5.1/vcedit.c:156:15:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
			bytes = s->read(buffer,1, CHUNKSIZE, s->in);
data/poe.app-0.5.1/vcedit.c:201:17:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	bytes = state->read(buffer, 1, CHUNKSIZE, state->in);
data/poe.app-0.5.1/vcedit.c:280:18:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
		bytes = state->read(buffer, 1, CHUNKSIZE, state->in);
data/poe.app-0.5.1/vcedit.c:290:25:  [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).
	state->vendor = malloc(strlen(state->vc->vendor) +1);
data/poe.app-0.5.1/vcedit.c:454:18:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
		bytes = state->read(buffer,1, CHUNKSIZE, state->in);
data/poe.app-0.5.1/vcedit.h:34:19:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	vcedit_read_func read;

ANALYSIS SUMMARY:

Hits = 12
Lines analyzed = 1115 in approximately 0.06 seconds (17397 lines/second)
Physical Source Lines of Code (SLOC) = 678
Hits@level = [0]  12 [1]   8 [2]   3 [3]   0 [4]   1 [5]   0
Hits@level+ = [0+]  24 [1+]  12 [2+]   4 [3+]   1 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 35.3982 [1+] 17.6991 [2+] 5.89971 [3+] 1.47493 [4+] 1.47493 [5+]   0
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.