AI Slop Code Risk Monitor

nvim-treesitter/nvim-treesitter

Name: nvim-treesitter/nvim-treesitter — Tree-sitter Query 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).

Nvim Treesitter configurations and abstraction layer

2.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for nvim-treesitter/nvim-treesitter, a Tree-sitter Query project with 14,498 GitHub stars. SynthScan examined 13,941 lines of code across 308 source files, recording 41 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.9 (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.9

Adjusted Signal

2.9

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

14.5K

Stars

Tree-sitter Query

Language

13.9K

Lines of Code

308

Files

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

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

Hallucinated Dependency & Supply Chain Risk 1.1/100 · LOW

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

Agent Over-Engineering Ratio 0.4/100 · LOW

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

PR Review Velocity Impact 13.7/100 · LOW

Which changes need focused human review? 41 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 41

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 41 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 Block36 hits · 36 pts

Severity	File	Line	Snippet	Context
LOW	tests/indent/r/comment.R	1	# some	COMMENT
LOW	tests/query/highlights/python/fields.py	1	class Fields:	COMMENT
LOW	tests/query/highlights/python/future_import.py	1	from __future__ import print_function	COMMENT
LOW	tests/query/highlights/python/docstrings.py	41	single_line_implicit_string_concatenation = "abc" "def"	COMMENT
LOW	tests/query/highlights/python/regex.py	1	import re	COMMENT
LOW	tests/query/highlights/rust/super-crate-imports.rs	1	use crate::a;	COMMENT
LOW	tests/query/highlights/rust/parameters.rs	1	pub fn func(ref root: &mut Element, ref mut param2: u32) {	COMMENT
LOW	tests/query/highlights/r/test.r	1	init <- 1	COMMENT
LOW	tests/query/highlights/r/test.r	21		COMMENT
LOW	tests/query/highlights/php/keywords.php	21	};	COMMENT
LOW	tests/query/highlights/php/keywords.php	41	{	COMMENT
LOW	tests/query/highlights/php/namespaces.php	21	// ^^^ @function	COMMENT
LOW	tests/query/highlights/php/namespaces.php	41	// ^^^^ @constant	COMMENT
LOW	tests/query/highlights/php/namespaces.php	61	const FOO as FOOO,	COMMENT
LOW	tests/query/highlights/php/namespaces.php	81	// ^^^ @function.call	COMMENT
LOW	tests/query/highlights/php/namespaces.php	101	// ^^^ @constructor	COMMENT
LOW	tests/query/highlights/php/namespaces.php	121	// ^^^ @constant	COMMENT
LOW	tests/query/highlights/cpp/test.cpp	1	#include <iostream>	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	1	#!/bin/zsh	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	21	# Function definition	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	41	#^^^ @function.call @function.builtin @number	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	61	# ^^^^ @keyword.conditional	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	81	done	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	101	"yes"\|"y")	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	121	*)	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	141	# ^ @punctuation.special	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	161	#^^^^^ @variable @constant	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	181		COMMENT
LOW	tests/query/highlights/zsh/test.zsh	201	# Test commands	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	221	# ^ @number	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	241		COMMENT
LOW	tests/query/highlights/zsh/test.zsh	261	# ^^ @punctuation.special @none @variable.builtin	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	281	# ^^ @operator	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	301	# ^^^^^^^^ @string.special.path @number	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	321	# ^ punctuation.bracket	COMMENT
LOW	tests/query/highlights/zsh/test.zsh	341	#^^^ @function.call @function.builtin @number	COMMENT

Unused Imports3 hits · 3 pts

Severity	File	Line	Context
LOW	tests/indent/python/basic_blocks.py	1	CODE
LOW	tests/indent/python/basic_blocks.py	1	CODE
LOW	tests/query/highlights/python/future_import.py	1	CODE

Excessive Try-Catch Wrapping1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	tests/query/highlights/python/raise_from.py	3	except Exception:	CODE

Overly Generic Function Names1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	tests/query/highlights/ecma/test.ts	27	function doSomething(options) {	CODE