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/pink-pony-1.4.1/external/flextGL/flextGL.c
Examining data/pink-pony-1.4.1/external/flextGL/flextGL.h
Examining data/pink-pony-1.4.1/src/Animation.cc
Examining data/pink-pony-1.4.1/src/Camera.cc
Examining data/pink-pony-1.4.1/src/Heightmap.cc
Examining data/pink-pony-1.4.1/src/Line.cc
Examining data/pink-pony-1.4.1/src/LineList.cc
Examining data/pink-pony-1.4.1/src/Mesh.cc
Examining data/pink-pony-1.4.1/src/MeshDrawer.cc
Examining data/pink-pony-1.4.1/src/ParticleSystem.cc
Examining data/pink-pony-1.4.1/src/PonyPoints.cc
Examining data/pink-pony-1.4.1/src/Shader.cc
Examining data/pink-pony-1.4.1/src/Skydome.cc
Examining data/pink-pony-1.4.1/src/Texture2D.cc
Examining data/pink-pony-1.4.1/src/Transform.cc
Examining data/pink-pony-1.4.1/src/TransformFeedback.cc
Examining data/pink-pony-1.4.1/src/Widget.cc
Examining data/pink-pony-1.4.1/src/utilities.cc
Examining data/pink-pony-1.4.1/src/Config.cc
Examining data/pink-pony-1.4.1/src/Menu.cc
Examining data/pink-pony-1.4.1/src/Pony.cc
Examining data/pink-pony-1.4.1/src/PonyGame.cc
Examining data/pink-pony-1.4.1/src/SplitScreen.cc
Examining data/pink-pony-1.4.1/src/main.cc
Examining data/pink-pony-1.4.1/tools/mesh_compile.cc
Examining data/pink-pony-1.4.1/tools/skeleton_compile.cc

FINAL RESULTS:

data/pink-pony-1.4.1/external/flextGL/flextGL.h:6342:82:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
typedef GLvoid* (APIENTRY PFNGLMAPBUFFER_PROC (const GLenum target, const GLenum access));
data/pink-pony-1.4.1/src/ParticleSystem.cc:383:60:  [4] (shell) system:
  This causes a new program to execute and is difficult to use safely
  (CWE-78). try using a library call that implements the same functionality
  if available.
StaticParticleSource::StaticParticleSource(ParticleSystem* system,
data/pink-pony-1.4.1/src/ParticleSystem.cc:387:22:  [4] (shell) system:
  This causes a new program to execute and is difficult to use safely
  (CWE-78). try using a library call that implements the same functionality
  if available.
    : ParticleSource(system),
data/pink-pony-1.4.1/src/ParticleSystem.cc:415:56:  [4] (shell) system:
  This causes a new program to execute and is difficult to use safely
  (CWE-78). try using a library call that implements the same functionality
  if available.
PonyParticleSource::PonyParticleSource(ParticleSystem* system)
data/pink-pony-1.4.1/src/ParticleSystem.cc:416:22:  [4] (shell) system:
  This causes a new program to execute and is difficult to use safely
  (CWE-78). try using a library call that implements the same functionality
  if available.
    : ParticleSource(system),
data/pink-pony-1.4.1/src/ParticleSystem.cc:489:66:  [4] (shell) system:
  This causes a new program to execute and is difficult to use safely
  (CWE-78). try using a library call that implements the same functionality
  if available.
ParticleExplosionSource::ParticleExplosionSource(ParticleSystem* system)
data/pink-pony-1.4.1/src/ParticleSystem.cc:490:22:  [4] (shell) system:
  This causes a new program to execute and is difficult to use safely
  (CWE-78). try using a library call that implements the same functionality
  if available.
    : ParticleSource(system),
data/pink-pony-1.4.1/src/Shader.cc:15:8:  [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(file_name.c_str());
data/pink-pony-1.4.1/src/Shader.cc:28: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 logBuffer[LOG_BUFFER_SIZE];
data/pink-pony-1.4.1/src/Shader.cc:41: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 logBuffer[LOG_BUFFER_SIZE];
data/pink-pony-1.4.1/src/TransformFeedback.cc:44:9:  [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 name[100];
data/pink-pony-1.4.1/src/TransformFeedback.cc:163:13:  [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 name[100];
data/pink-pony-1.4.1/src/ParticleSystem.cc:79:29:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    for (unsigned read = 0; read < particle_count; ++read) {
data/pink-pony-1.4.1/src/ParticleSystem.cc:79:54:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    for (unsigned read = 0; read < particle_count; ++read) {
data/pink-pony-1.4.1/src/ParticleSystem.cc:80:40:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
        if (step_particle(time_diff, p[read], p[write])) {
data/pink-pony-1.4.1/src/utilities.cc:217:9:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
        strncpy(cs, s.data(), s.size()+1);

ANALYSIS SUMMARY:

Hits = 16
Lines analyzed = 13894 in approximately 0.35 seconds (39756 lines/second)
Physical Source Lines of Code (SLOC) = 11178
Hits@level = [0]   7 [1]   4 [2]   5 [3]   0 [4]   7 [5]   0
Hits@level+ = [0+]  23 [1+]  16 [2+]  12 [3+]   7 [4+]   7 [5+]   0
Hits/KSLOC@level+ = [0+] 2.05761 [1+] 1.43138 [2+] 1.07354 [3+] 0.62623 [4+] 0.62623 [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.