AI Slop Code Risk Monitor

jqlang/jq

Name: jqlang/jq — C Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

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

Command-line JSON processor

2.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for jqlang/jq, a C project with 35,992 GitHub stars. SynthScan examined 56,395 lines of code across 102 source files, recording 118 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 2.0 (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.0

Adjusted Signal

2.0

Raw Pattern Score

100%

Time Factor

2026-10-25

Last Push

36.0K

Stars

Language

56.4K

Lines of Code

102

Files

118

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 9.7/100 · LOW

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

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

PR Review Velocity Impact 9.9/100 · LOW

Which changes need focused human review? 118 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 0LOW 118

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 118 distinct pattern matches across 3 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 Block115 hits · 112 pts

Severity	File	Line	Snippet	Context
LOW	src/bytecode.c	1	#include <stdio.h>	COMMENT
LOW	src/jv_dtoa.c	201		COMMENT
LOW	src/jv_dtoa.c	221	#endif	COMMENT
LOW	src/jv_dtoa.c	241	#define IEEE_Arith	COMMENT
LOW	src/jv_dtoa.c	261	#define DBL_MAX_EXP 1024	COMMENT
LOW	src/jv_dtoa.c	281	#ifndef LONG_MAX	COMMENT
LOW	src/jv_dtoa.c	301	#if defined(IEEE_8087) + defined(IEEE_MC68k) + defined(VAX) + defined(IBM) != 1	COMMENT
LOW	src/jv_dtoa.c	341	/* Quick_max = floor((P-1)log(FLT_RADIX)/log(10) - 1) /	COMMENT
LOW	src/jv_dtoa.c	361	#define Bletch 0x10	COMMENT
LOW	src/jv_dtoa.c	381	#else	COMMENT
LOW	src/jv_dtoa.c	401	#define Flt_Rounds 0	COMMENT
LOW	src/jv_dtoa.c	421	#define LSB 1	COMMENT
LOW	src/jv_dtoa.c	441	#define Exp_1 0x40800000	COMMENT
LOW	src/jv_dtoa.c	461	#define ROUND_BIASED	COMMENT
LOW	src/jv_dtoa.c	1381	#else	COMMENT
LOW	src/linker.c	1	#include <assert.h>	COMMENT
LOW	src/util.c	21	* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR	COMMENT
LOW	src/util.c	41	# include <alloca.h>	COMMENT
LOW	src/util.c	481	#define TM_YEAR_BASE 1900	COMMENT
LOW	src/util.c	501	#define HAVE_YDAY(s) (s & S_YDAY)	COMMENT
LOW	src/jv_parse.c	1	#include <stdio.h>	COMMENT
LOW	src/jv.c	81	typedef enum {	COMMENT
LOW	src/jq_test.c	1	#include <assert.h>	COMMENT
LOW	src/parser.h	121	};	COMMENT
LOW	src/parser.h	141	#define DEF 270	COMMENT
LOW	src/parser.h	161	#define SETMINUS 290	COMMENT
LOW	src/execute.c	1	#include <assert.h>	COMMENT
LOW	src/lexer.c	1	#line 1 "src/lexer.c"	COMMENT
LOW	src/lexer.c	21	#endif	COMMENT
LOW	src/lexer.c	41	#ifdef yy_scan_bytes	COMMENT
LOW	src/lexer.c	61	#else	COMMENT
LOW	src/lexer.c	81	#endif	COMMENT
LOW	src/lexer.c	101	#ifdef yylex_init	COMMENT
LOW	src/lexer.c	121	#else	COMMENT
LOW	src/lexer.c	141	#endif	COMMENT
LOW	src/lexer.c	161	#ifdef yyset_out	COMMENT
LOW	src/lexer.c	181	#else	COMMENT
LOW	src/lexer.c	201	#endif	COMMENT
LOW	src/lexer.c	221	#ifdef yyget_lloc	COMMENT
LOW	src/lexer.c	241	#else	COMMENT
LOW	src/lexer.c	301	#endif	COMMENT
LOW	src/lexer.c	321	#ifndef SIZE_MAX	COMMENT
LOW	src/lexer.c	821	static int try_exit(int closing, int state, yyscan_t yyscanner);	COMMENT
LOW	src/lexer.c	941	extern "C" int yywrap ( yyscan_t yyscanner );	COMMENT
LOW	src/jv_aux.c	1	#include <assert.h>	COMMENT
LOW	src/compile.h	81		COMMENT
LOW	src/main.c	1	#include <assert.h>	COMMENT
LOW	src/main.c	21	extern void jv_tsd_dtoa_ctx_init();	COMMENT
LOW	src/jv.h	1	#ifndef JV_H	COMMENT
LOW	src/jv.h	101	#define jv_array_foreach(a, i, x) \	COMMENT
LOW	src/jv.h	181	for (jv k; \	COMMENT
LOW	src/util.h	1	#ifndef UTIL_H	COMMENT
LOW	src/builtin.c	1	#if __SIZEOF_POINTER__==4	COMMENT
LOW	src/builtin.c	21	#ifdef HAVE_LIBONIG	COMMENT
LOW	src/builtin.c	101	return jv_array_concat(a, b);	COMMENT
LOW	src/builtin.c	121	#define drem remainder	COMMENT
LOW	src/builtin.c	221	return ret; \	COMMENT
LOW	src/builtin.c	2021	#define LIBM_DD(name) \	COMMENT
LOW	src/lexer.h	1	#ifndef jq_yyHEADER_H	COMMENT
LOW	src/lexer.h	21	#ifdef yy_create_buffer	COMMENT
55 more matches not shown…

Deep Nesting2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	docs/build_manpage.py	208		CODE
LOW	docs/build_manpage.py	64		CODE

Hyper-Verbose Identifiers1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	docs/build_manpage.py	208	def convert_manual_to_markdown():	CODE