AI Slop Code Risk Monitor

ocaml/dune

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

A composable build system for OCaml.

3.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for ocaml/dune, a OCaml project with 1,933 GitHub stars. SynthScan examined 27,165 lines of code across 436 source files, recording 68 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 3.5 (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.

3.5
Adjusted Signal
3.5
Raw Pattern Score
100%
Time Factor
2026-11-01
Last Push
1.9K
Stars
OCaml
Language
27.2K
Lines of Code
436
Files
68
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 15.4/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 67 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.6/100 · LOW

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

PR Review Velocity Impact 15.6/100 · LOW

Which changes need focused human review? 68 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 12LOW 56

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 68 distinct pattern matches across 6 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 Block52 hits · 52 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.c181COMMENT
LOWotherlibs/stdune/src/spawn_stubs.c201COMMENT
LOWotherlibs/stdune/src/spawn_stubs.c221# endifCOMMENT
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.yml161 #COMMENT
LOWdoc/conf.py1#!/usr/bin/env python3COMMENT
LOWdoc/conf.py161COMMENT
LOWdoc/changes/scripts/build_changelog.sh1#!/usr/bin/env bashCOMMENT
LOWdoc/changes/scripts/build_changelog.sh21output=".changelog.new"COMMENT
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# - The optional DUNE_REPO is the repository whose CI results gate the release,COMMENT
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.c41#define SYS___pthread_chdir 348COMMENT
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.sh97# 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.yml45 # 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.sh33# Set DUNE_REMOTE to the matching dune fork remote so the release branch andCOMMENT