Home / erincatto / box3d
AI Slop Code Risk Monitor

erincatto/box3d

SlopCodeMonitor badge for erincatto/box3d Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Box3D is a 3D physics engine for games

2.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for erincatto/box3d, a C project with 6,728 GitHub stars. SynthScan examined 185,579 lines of code across 282 source files, recording 431 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.3 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

2.3
Adjusted Signal
2.3
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
6.7K
Stars
C
Language
185.6K
Lines of Code
282
Files
431
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 11.0/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 431 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 0 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 0 finding(s).

PR Review Velocity Impact 11.2/100 · LOW

Which changes need focused human review? 431 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 4LOW 427

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 431 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block413 hits · 399 pts
SeverityFileLineSnippetContext
LOWbenchmark/main.c1// SPDX-FileCopyrightText: 2025 Erin CattoCOMMENT
LOWbenchmark/main.c201// start /affinity 0x5555 .\build\bin\Release\benchmark.exe -t=4 -w=4COMMENT
LOWtest/test_manifold.c1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWtest/test_hash.c1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWtest/test_determinism.c1// SPDX-FileCopyrightText: 2025 Erin CattoCOMMENT
LOWtest/test_determinism.c21#if defined( BOX3D_DOUBLE_PRECISION )COMMENT
LOWtest/test_determinism.c41#define MESH_DROP_SLEEP_STEP 226COMMENT
LOWtest/test_body_query.c1// SPDX-FileCopyrightText: 2025 Erin CattoCOMMENT
LOWtest/test_sat.c1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWtest/test_world.c1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWtest/test_restitution.c1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWtest/test_restitution.c881 result.peakEnergyRatio );COMMENT
LOWtest/test_compound.c1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWtest/test_broad_phase.c1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWtest/test_recording.c1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWtest/test_body.c1// SPDX-FileCopyrightText: 2025 Erin CattoCOMMENT
LOWtest/main.c1// SPDX-FileCopyrightText: 2024 Erin CattoCOMMENT
LOWtest/test_mesh.c1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWtest/test_dynamic_tree.c1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWinclude/box3d/config.h1// SPDX-FileCopyrightText: 2026 Erin CattoCOMMENT
LOWinclude/box3d/config.h21//#define BOX3D_DISABLE_SIMDCOMMENT
LOWinclude/box3d/types.h1// SPDX-FileCopyrightText: 2025 Erin CattoCOMMENT
LOWinclude/box3d/types.h21/// @ingroup worldCOMMENT
LOWinclude/box3d/types.h41/// do not call b3World_Step from inside a job: a job that blocks on its own sub-jobs withoutCOMMENT
LOWinclude/box3d/types.h61 uint64_t userMaterialIdB );COMMENT
LOWinclude/box3d/types.h81typedef bool b3CustomFilterFcn( b3ShapeId shapeIdA, b3ShapeId shapeIdB, void* context );COMMENT
LOWinclude/box3d/types.h101/// @see b3World_OverlapAABBCOMMENT
LOWinclude/box3d/types.h301COMMENT
LOWinclude/box3d/types.h341 /// Use this to store application specific body data.COMMENT
LOWinclude/box3d/types.h361 /// using them for game projectiles if precise collision timing is needed. Instead considerCOMMENT
LOWinclude/box3d/types.h381 /// Used internally to detect a valid definition. DO NOT SET.COMMENT
LOWinclude/box3d/types.h401 /// Debris = 0x00000004,COMMENT
LOWinclude/box3d/types.h521 /// Enable custom filtering. Only one of the two shapes needs to enable custom filtering. SeeCOMMENT
LOWinclude/box3d/types.h541 /// sensors. False by default.COMMENT
LOWinclude/box3d/types.h1021 /// velocity between the two bodies in world space.COMMENT
LOWinclude/box3d/types.h1181/// a filter. You will also get an end event if the sensor or visitor are destroyed.COMMENT
LOWinclude/box3d/types.h1221 b3ShapeId shapeIdB;COMMENT
LOWinclude/box3d/types.h1301 /// Number of end touch eventsCOMMENT
LOWinclude/box3d/types.h1401COMMENT
LOWinclude/box3d/types.h1901/// This function receives proxies found in the AABB query.COMMENT
LOWinclude/box3d/types.h2581COMMENT
LOWinclude/box3d/collision.h41COMMENT
LOWinclude/box3d/collision.h61COMMENT
LOWinclude/box3d/collision.h261/// @param hx, hy, hz positive half widthsCOMMENT
LOWinclude/box3d/collision.h581typedef bool b3MeshQueryFcn( b3Vec3 a, b3Vec3 b, b3Vec3 c, int triangleIndex, void* context );COMMENT
LOWinclude/box3d/id.h81#elseCOMMENT
LOWinclude/box3d/box3d.h21 * debug draw, timing information, and counters. You can find documentation here: https://box2d.org/COMMENT
LOWinclude/box3d/box3d.h41/// Get the current number of worldsCOMMENT
LOWinclude/box3d/box3d.h81COMMENT
LOWinclude/box3d/box3d.h121/// Cast a capsule mover through the world. This is a special shape cast that handles sliding alongCOMMENT
LOWinclude/box3d/box3d.h201/// Get the gravity vectorCOMMENT
LOWinclude/box3d/box3d.h301COMMENT
LOWinclude/box3d/box3d.h321COMMENT
LOWinclude/box3d/box3d.h361/// @param size byte count of the recordingCOMMENT
LOWinclude/box3d/box3d.h401COMMENT
LOWinclude/box3d/box3d.h441B3_API int b3RecPlayer_GetBodyCount( const b3RecPlayer* player );COMMENT
LOWinclude/box3d/box3d.h521 * @defgroup body BodyCOMMENT
LOWinclude/box3d/box3d.h601/// The result will be close but maybe not exact. This is meant for kinematic bodies.COMMENT
LOWinclude/box3d/box3d.h621COMMENT
LOWinclude/box3d/box3d.h641/// @param impulse the world impulse vector, usually in N*s or kg*m/s.COMMENT
353 more matches not shown…
AI Slop Vocabulary4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUMsamples/sample_replay.cpp1866 // A pinned query prefers its identity key (the hash of the caller id and label), the robust identityCOMMENT
MEDIUMsamples/tiny_obj_loader.h35// * Add robust triangulation using MapboxCOMMENT
MEDIUMsamples/tiny_obj_loader.h1276 // @todo { write more robust lexer and parser. }COMMENT
MEDIUM.github/workflows/build.yml137 # Build-only: running the wasm test needs a node + pthread/SharedArrayBuffer harness.COMMENT
Verbosity Indicators7 hits · 10 pts
SeverityFileLineSnippetContext
LOWsrc/mesh_contact.c308 // Step 1: the two points with the largest distance, ties broken by deepest combined separationCOMMENT
LOWsrc/mesh_contact.c376 // Step 2: find the point with the maximum triangular area, ties broken by deepest separationCOMMENT
LOWsrc/mesh_contact.c419 // Step 4: get the point that adds the most area outside the current triangleCOMMENT
LOWsrc/convex_manifold.c819 // Step 1: find extreme point that is touchingCOMMENT
LOWsrc/convex_manifold.c862 // Step 2: Find farthest point in 2DCOMMENT
LOWsrc/convex_manifold.c896 // Step 3: Find the point with the maximum triangular areaCOMMENT
LOWsrc/convex_manifold.c928 // Step 4: get the point that adds the most area outside the current triangleCOMMENT
Structural Annotation Overuse7 hits · 10 pts
SeverityFileLineSnippetContext
LOWsrc/mesh_contact.c308 // Step 1: the two points with the largest distance, ties broken by deepest combined separationCOMMENT
LOWsrc/mesh_contact.c376 // Step 2: find the point with the maximum triangular area, ties broken by deepest separationCOMMENT
LOWsrc/mesh_contact.c419 // Step 4: get the point that adds the most area outside the current triangleCOMMENT
LOWsrc/convex_manifold.c819 // Step 1: find extreme point that is touchingCOMMENT
LOWsrc/convex_manifold.c862 // Step 2: Find farthest point in 2DCOMMENT
LOWsrc/convex_manifold.c896 // Step 3: Find the point with the maximum triangular areaCOMMENT
LOWsrc/convex_manifold.c928 // Step 4: get the point that adds the most area outside the current triangleCOMMENT