Repository Analysis

ocaml/dune

A composable build system for OCaml.

3.7 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of ocaml/dune, a OCaml project with 1,907 GitHub stars. SynthScan v2.0 examined 24,861 lines of code across 326 source files, recording 66 pattern matches distributed across 6 syntactic categories. The overall adjusted score of 3.7 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.7
Adjusted Score
3.7
Raw Score
100%
Time Factor
2026-08-09
Last Push
1.9K
Stars
OCaml
Language
24.9K
Lines of Code
326
Files
66
Pattern Hits
2026-08-09
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 12LOW 54

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 66 distinct pattern matches across 6 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 Block50 hits · 50 pts
SeverityFileLineSnippetContext
LOW…test-cases/include-subdirs/test3.t/include/dune_test.h1#include <caml/mlvalues.h>COMMENT
LOW…ts/test-cases/foreign-stubs/cpp-std-ocaml5.t/cpp11.cpp1#include <iostream>COMMENT
LOWotherlibs/stdune/src/wait4_stubs.c21#include <caml/unixsupport.h>COMMENT
LOWotherlibs/stdune/src/spawn_stubs.c1#define _GNU_SOURCECOMMENT
LOWotherlibs/stdune/src/spawn_stubs.c21#include <caml/unixsupport.h>COMMENT
LOWotherlibs/stdune/src/spawn_stubs.c41#include <sys/socket.h>COMMENT
LOWotherlibs/stdune/src/spawn_stubs.c81COMMENT
LOWotherlibs/stdune/src/dune_clock.h1// Cross-platform realtime clock with legacy fallbacksCOMMENT
LOWotherlibs/stdune/src/time_stubs.c1#if defined(__APPLE__)COMMENT
LOWotherlibs/stdune/src/signal_stubs.c1#include <caml/mlvalues.h>COMMENT
LOWotherlibs/stdune/src/copyfile_stubs.c1#include <caml/fail.h>COMMENT
LOW.github/workflows/workflow.yml141COMMENT
LOWdoc/conf.py1#!/usr/bin/env python3COMMENT
LOWdoc/conf.py161COMMENT
LOWdoc/changes/scripts/build_changelog.sh1#!/usr/bin/env bashCOMMENT
LOWdoc/dev/releases/backport.sh1#!/usr/bin/env bashCOMMENT
LOWdoc/dev/releases/backport.sh21#COMMENT
LOWdoc/dev/releases/release-init.sh1#!/usr/bin/env bashCOMMENT
LOWdoc/dev/releases/release-cut.sh1#!/usr/bin/env bashCOMMENT
LOWdoc/dev/releases/release-cut.sh21# - NB. To stage a release against forks, dune-release reads the following fromCOMMENT
LOWdoc/howto/use-multiple-build-contexts.md101 #7 caml_startup runtime/startup_nat.c:144 (tsan_check.exe+0xdc29b)COMMENT
LOWdoc/howto/use-multiple-build-contexts.md121 #8 caml_main runtime/startup_nat.c:151 (tsan_check.exe+0xdc29b)COMMENT
LOWsrc/dune_trace/dune_trace_stubs.c1#include <caml/alloc.h>COMMENT
LOWsrc/lev/src/config.h1// TODO port supportCOMMENT
LOWsrc/lev/src/config.h21#define HAVE_SELECT 1COMMENT
LOWsrc/lev/src/config.h41#define HAVE_SIGNALFD_H 1COMMENT
LOWsrc/lev/src/config.h61#if __has_include(<sys/event.h>)COMMENT
LOWsrc/lev/src/lev_stubs.c1#include "ev.h"COMMENT
LOWsrc/lev/src/lev_stubs.c21#include <caml/callback.h>COMMENT
LOWsrc/dune_scheduler/fsevents_stubs.c1#include <caml/alloc.h>COMMENT
LOWsrc/dune_scheduler/fswatch_win_stubs.c21 object which causes the [wait] function to return.COMMENT
LOWsrc/dune_scheduler/fswatch_win_stubs.c41#define caml_uerror uerrorCOMMENT
LOWsrc/ocaml-blake3-mini/blake3_stubs.c1#include <errno.h>COMMENT
LOWsrc/ocaml-blake3-mini/blake3.h1#ifndef BLAKE3_HCOMMENT
LOWsrc/ocaml-blake3-mini/blake3.h21# define BLAKE3_API __attribute__((visibility("default")))COMMENT
LOWsrc/ocaml-blake3-mini/blake3_dispatch.c1#include <stdbool.h>COMMENT
LOWsrc/ocaml-blake3-mini/blake3_dispatch.c21#if !defined(BLAKE3_ATOMICS)COMMENT
LOWsrc/ocaml-blake3-mini/blake3.c261// wouldn't be able to implement extendable output.) Note that this function isCOMMENT
LOWsrc/ocaml-blake3-mini/blake3.c281 // With more than simd_degree chunks, we need to recurse. Start by dividingCOMMENT
LOWsrc/ocaml-blake3-mini/blake3.c361 // The following loop never executes when MAX_SIMD_DEGREE_OR_2 is 2, becauseCOMMENT
LOWsrc/ocaml-blake3-mini/blake3.c441// If the user gives us 64 KiB, we want to parallelize over all 64 KiB at onceCOMMENT
LOWsrc/ocaml-blake3-mini/blake3.c501 uint8_t chunk_cv[32];COMMENT
LOWsrc/ocaml-blake3-mini/blake3.c521 // Because we might need to break up the input to form powers of 2, or toCOMMENT
LOWsrc/ocaml-blake3-mini/blake3_impl.h1#ifndef BLAKE3_IMPL_HCOMMENT
LOWsrc/ocaml-blake3-mini/blake3_impl.h21 ROOT = 1 << 3,COMMENT
LOWsrc/ocaml-blake3-mini/blake3_impl.h41#if (defined(__x86_64__) || defined(_M_X64)) && !defined(_M_ARM64EC)COMMENT
LOWsrc/ocaml-blake3-mini/blake3_impl.h61#if !defined(BLAKE3_USE_NEON) COMMENT
LOWsrc/dune_pkg/md5_stubs.c1#define CAML_INTERNALS // needed to access md5.h functionsCOMMENT
LOWsrc/rpc/csexp_rpc_stubs.c1#include <caml/alloc.h>COMMENT
LOWsrc/rpc/csexp_rpc_stubs.c21}COMMENT
Self-Referential Comments10 hits · 30 pts
SeverityFileLineSnippetContext
MEDIUMtest/blackbox-tests/test-cases/pkg/ocamllsp/helpers.sh3# Create a dune-workspace file with mock repos set up for the mainCOMMENT
MEDIUMtest/blackbox-tests/test-cases/pkg/ocamllsp/helpers.sh9# Create a fake ocaml-lsp-server package containing an executable thatCOMMENT
MEDIUMtest/blackbox-tests/test-cases/pkg/merlin/helpers.sh3# Create a dune-workspace file with mock repos configured for the mainCOMMENT
MEDIUMtest/blackbox-tests/test-cases/pkg/merlin/helpers.sh9# Create a fake merlin package containing an executable thatCOMMENT
MEDIUMtest/blackbox-tests/test-cases/pkg/odoc/helpers.sh3# Create a dune-workspace file with mock repos set up for the mainCOMMENT
MEDIUMtest/blackbox-tests/test-cases/pkg/odoc/helpers.sh9# Create a fake odoc package containing an executable thatCOMMENT
MEDIUM.github/workflows/workflow.yml1# This file is auto-generated. Edit workflow.yml.in insteadCOMMENT
MEDIUM.github/workflows/bench.yml1# This file is auto-generated. Edit bench.yml.in insteadCOMMENT
MEDIUMdoc/conf.py7# This file is execfile()d with the current directory set to itsCOMMENT
MEDIUMdoc/changes/scripts/build_changelog.sh95# Create the output fileCOMMENT
Example Usage Blocks3 hits · 4 pts
SeverityFileLineSnippetContext
LOWdoc/dev/releases/backport.sh8# Usage:COMMENT
LOWdoc/dev/releases/release-init.sh8# Usage:COMMENT
LOWdoc/dev/releases/release-cut.sh8# Usage:COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/revdeps-release-coverage.yml36 # robust tests we want to runCOMMENT
Decorative Section Separators1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMdoc/changes/scripts/build_changelog.sh33# -------------------COMMENT
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWdoc/dev/releases/release-cut.sh30# Set DUNE_REMOTE to the matching dune fork remote so the release branch andCOMMENT