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/pasmo-0.5.3/asm.h
Examining data/pasmo-0.5.3/asm.cpp
Examining data/pasmo-0.5.3/asmfile.h
Examining data/pasmo-0.5.3/asmfile.cpp
Examining data/pasmo-0.5.3/cpc.h
Examining data/pasmo-0.5.3/cpc.cpp
Examining data/pasmo-0.5.3/pasmotypes.h
Examining data/pasmo-0.5.3/pasmotypes.cpp
Examining data/pasmo-0.5.3/spectrum.h
Examining data/pasmo-0.5.3/spectrum.cpp
Examining data/pasmo-0.5.3/tap.h
Examining data/pasmo-0.5.3/tap.cpp
Examining data/pasmo-0.5.3/token.h
Examining data/pasmo-0.5.3/token.cpp
Examining data/pasmo-0.5.3/tzx.h
Examining data/pasmo-0.5.3/tzx.cpp
Examining data/pasmo-0.5.3/pasmo.cpp

FINAL RESULTS:

data/pasmo-0.5.3/asm.cpp:5185: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 buffer [1024];
data/pasmo-0.5.3/asm.cpp:5804:3:  [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 aux [128]= {};
data/pasmo-0.5.3/asm.cpp:6310: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 fillhead [128 - 72]= { };
data/pasmo-0.5.3/asm.cpp:6314: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 prefix [256]= { };
data/pasmo-0.5.3/asmfile.cpp:332:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	is.open (filename.c_str (), mode);
data/pasmo-0.5.3/asmfile.cpp:340:6:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
		is.open (path.c_str (), mode);
data/pasmo-0.5.3/pasmo.cpp:330:9:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
			sout.open (filesymbol.c_str () );
data/pasmo-0.5.3/pasmo.cpp:351:9:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
			sout.open (filepublic.c_str () );
data/pasmo-0.5.3/token.cpp:545:6:  [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 x [3]= { 0 };
data/pasmo-0.5.3/asm.cpp:5188:5:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
		f.read (buffer, sizeof (buffer) );

ANALYSIS SUMMARY:

Hits = 10
Lines analyzed = 10022 in approximately 0.17 seconds (57297 lines/second)
Physical Source Lines of Code (SLOC) = 8177
Hits@level = [0]   0 [1]   1 [2]   9 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  10 [1+]  10 [2+]   9 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 1.22294 [1+] 1.22294 [2+] 1.10065 [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.