Repository Analysis

jrouwe/JoltPhysics

A multi core friendly rigid body physics and collision detection library. Written in C++. Suitable for games and VR applications. Used by Horizon Forbidden West and Death Stranding 2.

3.1 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of jrouwe/JoltPhysics, a C++ project with 10,898 GitHub stars. SynthScan v2.0 examined 193,839 lines of code across 1098 source files, recording 637 pattern matches distributed across 5 syntactic categories. The overall adjusted score of 3.1 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

3.1
Adjusted Score
3.1
Raw Score
100%
Time Factor
2026-07-12
Last Push
10.9K
Stars
C++
Language
193.8K
Lines of Code
1.1K
Files
637
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.

No multi-scan history yet — run the scanner again to build trend data.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 0MEDIUM 2LOW 635

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 637 distinct pattern matches across 5 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Over-Commented Block631 hits · 596 pts
SeverityFileLineSnippetContext
LOWHelloWorld/HelloWorld.cpp1// Jolt Physics Library (https://github.com/jrouwe/JoltPhysics)COMMENT
LOWHelloWorld/HelloWorld.cpp221COMMENT
LOWHelloWorld/HelloWorld.cpp261 // Create mapping table from object layer to broadphase layerCOMMENT
LOWUnitTests/doctest.h1// =============================================================COMMENT
LOWUnitTests/doctest.h21// which uses the Boost Software License - Version 1.0COMMENT
LOWUnitTests/doctest.h41COMMENT
LOWUnitTests/doctest.h61COMMENT
LOWUnitTests/doctest.h81#ifdef _MSC_VERCOMMENT
LOWUnitTests/doctest.h101#endif // GCCCOMMENT
LOWUnitTests/doctest.h121// == COMPILER WARNINGS HELPERS ====================================================================COMMENT
LOWUnitTests/doctest.h141COMMENT
LOWUnitTests/doctest.h161#define DOCTEST_MSVC_SUPPRESS_WARNING_PUSHCOMMENT
LOWUnitTests/doctest.h321#ifndef DOCTEST_PARTS_PUBLIC_PLATFORMCOMMENT
LOWUnitTests/doctest.h341COMMENT
LOWUnitTests/doctest.h361// MSVC++ 8.0 _MSC_VER == 1400 (Visual Studio 2005)COMMENT
LOWUnitTests/doctest.h381COMMENT
LOWUnitTests/doctest.h401COMMENT
LOWUnitTests/doctest.h421#define DOCTEST_INTERFACE DOCTEST_SYMBOL_EXPORTCOMMENT
LOWUnitTests/doctest.h441#if DOCTEST_MSVCCOMMENT
LOWUnitTests/doctest.h461#ifndef DOCTEST_NORETURNCOMMENT
LOWUnitTests/doctest.h481#else // DOCTEST_MSVCCOMMENT
LOWUnitTests/doctest.h501COMMENT
LOWUnitTests/doctest.h521#endif // _LIBCPP_VERSIONCOMMENT
LOWUnitTests/doctest.h561#elseCOMMENT
LOWUnitTests/doctest.h601// should probably take a look at https://github.com/scottt/debugbreakCOMMENT
LOWUnitTests/doctest.h621#define DOCTEST_BREAK_INTO_DEBUGGER() /* NOLINTNEXTLINE(hicpp-no-assembler) */ \COMMENT
LOWUnitTests/doctest.h881// - if small - acts as a null terminator if strlen() is 23 (24 including the null terminator)COMMENT
LOWUnitTests/doctest.h2901#define DOCTEST_FUNC_SCOPE_END ()COMMENT
LOWUnitTests/doctest.h3221 doctest::assertType::assert_type, __FILE__, __LINE__, #__VA_ARGS__, __VA_ARGS__ \COMMENT
LOWUnitTests/doctest.h3241#define DOCTEST_CHECK_FALSE_MESSAGE(cond, ...) DOCTEST_FUNC_SCOPE_BEGIN { DOCTEST_INFO(__VA_ARGS__); DOCTEST_ASSERT_IMPLCOMMENT
LOWUnitTests/doctest.h3321#define DOCTEST_CHECK_THROWS(...) DOCTEST_ASSERT_THROWS_WITH((__VA_ARGS__), #__VA_ARGS__, DT_CHECK_THROWS, "")COMMENT
LOWUnitTests/doctest.h3341#define DOCTEST_CHECK_THROWS_MESSAGE(expr, ...) DOCTEST_FUNC_SCOPE_BEGIN { DOCTEST_INFO(__VA_ARGS__); DOCTEST_CHECK_THROCOMMENT
LOWUnitTests/doctest.h3401COMMENT
LOWUnitTests/doctest.h3421#define DOCTEST_REGISTER_EXCEPTION_TRANSLATOR(signature) \COMMENT
LOWUnitTests/doctest.h3441#define DOCTEST_REQUIRE(...) [&] { return __VA_ARGS__; }()COMMENT
LOWUnitTests/doctest.h3461DOCTEST_RELATIONAL_OP(eq, ==)COMMENT
LOWUnitTests/doctest.h3481#define DOCTEST_REQUIRE_GT(...) [&] { return doctest::detail::gt(__VA_ARGS__); }()COMMENT
LOWUnitTests/doctest.h3501 }()COMMENT
LOWUnitTests/doctest.h3521#define DOCTEST_REQUIRE_THROWS_AS(expr, ...) [&] { try { expr; } catch (__VA_ARGS__) { return true; } catch (...) { } reCOMMENT
LOWUnitTests/doctest.h3541#define DOCTEST_WARN(...) DOCTEST_FUNC_EMPTYCOMMENT
LOWUnitTests/doctest.h3561#define DOCTEST_WARN_GT(...) DOCTEST_FUNC_EMPTYCOMMENT
LOWUnitTests/doctest.h3581#ifndef DOCTEST_CONFIG_NO_EXCEPTIONSCOMMENT
LOWUnitTests/doctest.h3601#define DOCTEST_REQUIRE_THROWS_MESSAGE(expr, ...) DOCTEST_FUNC_EMPTYCOMMENT
LOWUnitTests/doctest.h3641#undef DOCTEST_REQUIRE_EQCOMMENT
LOWUnitTests/doctest.h3661#define DOCTEST_REQUIRE_UNARY_FALSE DOCTEST_EXCEPTION_EMPTY_FUNCCOMMENT
LOWUnitTests/doctest.h3681#define DOCTEST_WARN_THROWS_MESSAGE(expr, ...) DOCTEST_EXCEPTION_EMPTY_FUNCCOMMENT
LOWUnitTests/doctest.h3701#define DOCTEST_FAST_CHECK_EQ DOCTEST_CHECK_EQCOMMENT
LOWUnitTests/doctest.h3721#define DOCTEST_FAST_REQUIRE_UNARY DOCTEST_REQUIRE_UNARYCOMMENT
LOWUnitTests/doctest.h3741#define DOCTEST_AND_THEN(name) DOCTEST_SUBCASE(" And: " name)COMMENT
LOWUnitTests/doctest.h3761#define REGISTER_EXCEPTION_TRANSLATOR(signature) DOCTEST_REGISTER_EXCEPTION_TRANSLATOR(signature)COMMENT
LOWUnitTests/doctest.h3781#define CHECK(...) DOCTEST_CHECK(__VA_ARGS__)COMMENT
LOWUnitTests/doctest.h3801#define WARN_THROWS_WITH_MESSAGE(expr, with, ...) DOCTEST_WARN_THROWS_WITH_MESSAGE(expr, with, __VA_ARGS__)COMMENT
LOWUnitTests/doctest.h3821#define SCENARIO_METHOD(x, name) DOCTEST_SCENARIO_METHOD(x, name)COMMENT
LOWUnitTests/doctest.h3841#define WARN_LT(...) DOCTEST_WARN_LT(__VA_ARGS__)COMMENT
LOWUnitTests/doctest.h3861#define FAST_WARN_NE(...) DOCTEST_FAST_WARN_NE(__VA_ARGS__)COMMENT
LOWUnitTests/doctest.h3901COMMENT
LOWUnitTests/doctest.h3921#include <cstdlib>COMMENT
LOWUnitTests/doctest.h3941#define DOCTEST_DECLARE_STATIC_MUTEX(name)COMMENT
LOWUnitTests/doctest.h3961#endif // DOCTEST_PLATFORM_MACCOMMENT
LOWUnitTests/doctest.h3981#include <io.h>COMMENT
571 more matches not shown…
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMTestFramework/Renderer/VK/RendererVK.cpp572 // Test and utilize support for transient memory for the depth bufferCOMMENT
MEDIUMTestFramework/Renderer/VK/RendererVK.cpp579 // Test and utilize lazily allocated memory for the depth bufferCOMMENT
Slop Phrases2 hits · 3 pts
SeverityFileLineSnippetContext
LOWJolt/Physics/Vehicle/VehicleConstraint.h44/// Note: Don't forget to register the constraint as a StepListener with the PhysicsSystem!COMMENT
LOWJolt/Physics/Collision/PhysicsMaterial.h21/// If you inherit from this material, don't forget to create a suitable default material in sDefaultCOMMENT
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWAssets/export_face.py22def export_scene_meshes_to_bin(filepath):CODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWAssets/export_face.py22CODE