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/solfege-3.23.4/solfege/soundcard/macro_to_function.h
Examining data/solfege-3.23.4/solfege/soundcard/xmalloc.c
Examining data/solfege-3.23.4/solfege/soundcard/macro_to_function.c
Examining data/solfege-3.23.4/solfege/soundcard/fft.h
Examining data/solfege-3.23.4/solfege/soundcard/gate.h
Examining data/solfege-3.23.4/solfege/soundcard/fft.c
Examining data/solfege-3.23.4/solfege/soundcard/calc.c
Examining data/solfege-3.23.4/solfege/soundcard/solfege_c_midi.c
Examining data/solfege-3.23.4/solfege/soundcard/xmalloc.h
Examining data/solfege-3.23.4/solfege/soundcard/dsp.c
Examining data/solfege-3.23.4/solfege/soundcard/gate.c
Examining data/solfege-3.23.4/solfege/soundcard/dsp.h
Examining data/solfege-3.23.4/solfege/soundcard/winmidi.c
Examining data/solfege-3.23.4/solfege/soundcard/calc.h
Examining data/solfege-3.23.4/test/seq.c

FINAL RESULTS:

data/solfege-3.23.4/solfege/soundcard/dsp.c:78:18:  [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).
	if( ( dev->fd = open( dev->dev_name, dev->o_mode | O_NONBLOCK ) ) == -1 ) {
data/solfege-3.23.4/solfege/soundcard/dsp.c:322:4:  [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( fftbuf + _config.fft_points - bread, audiobuf, bread );
data/solfege-3.23.4/solfege/soundcard/dsp.c:324:4:  [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( fftbuf, audiobuf + bread - _config.fft_points, _config.fft_points ); 
data/solfege-3.23.4/solfege/soundcard/solfege_c_midi.c:100: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.
static char _tmpbuf[100];
data/solfege-3.23.4/solfege/soundcard/winmidi.c:58: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 errBuffer[MAXERRORLENGTH];
data/solfege-3.23.4/solfege/soundcard/winmidi.c:65: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(errBuffer, "Unrecognized MIDI error occurred (%d).", val);
data/solfege-3.23.4/solfege/soundcard/winmidi.c:68: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(errBuffer, "Invalid error parameter found while retrieving error %d.", val);
data/solfege-3.23.4/solfege/soundcard/winmidi.c:71: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(errBuffer, "Unknown error occurred while retrieving error %d.", val);
data/solfege-3.23.4/test/seq.c:29:22:  [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).
        if ((seqfd = open(SEQUENCER_DEV, O_WRONLY, 0)) < 0) {
data/solfege-3.23.4/solfege/soundcard/dsp.c:214:8:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
			if( read( dev->fd, dev->ptr, dev->buf_size ) == -1 )
data/solfege-3.23.4/solfege/soundcard/dsp.c:217:4:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
			read( dev->fd, dev->ptr, carrier );
data/solfege-3.23.4/solfege/soundcard/solfege_c_midi.c:110:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
  strncpy(_tmpbuf, si.name, 99);

ANALYSIS SUMMARY:

Hits = 12
Lines analyzed = 2169 in approximately 0.25 seconds (8648 lines/second)
Physical Source Lines of Code (SLOC) = 1544
Hits@level = [0]  15 [1]   3 [2]   9 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  27 [1+]  12 [2+]   9 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 17.487 [1+] 7.77202 [2+] 5.82902 [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.