AI Slop Code Risk Monitor

qpdf/qpdf

Name: qpdf/qpdf — 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).

qpdf: A content-preserving PDF document transformer

1.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for qpdf/qpdf, a C++ project with 5,541 GitHub stars. SynthScan examined 32,240 lines of code across 234 source files, recording 30 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.0

Adjusted Signal

1.0

Raw Pattern Score

100%

Time Factor

2026-09-26

Last Push

5.5K

Stars

C++

Language

32.2K

Lines of Code

234

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

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 4.8/100 · LOW

Which changes need focused human review? 30 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 1LOW 29

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 30 distinct pattern matches across 5 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 Block26 hits · 26 pts

Severity	File	Line	Snippet	Context
LOW	job.yml	341	# the help information. Otherwise, if the value is null, it has to	COMMENT
LOW	CMakeLists.txt	1	# manual/installation.rst mentions the minimum cmake version.	COMMENT
LOW	README-developer.md	761		COMMENT
LOW	libqpdf/sph/md_helper.c	81	#pragma warning (disable: 4146)	COMMENT
LOW	libqpdf/sph/md_helper.c	101	#define SPH_BLEN BLEN	COMMENT
LOW	libqpdf/sph/sph_types.h	841	#endif	COMMENT
LOW	libqpdf/sph/sph_types.h	941		COMMENT
LOW	libqpdf/sph/sph_types.h	1021	#elif defined __x86_64 \|\| defined _M_X64	COMMENT
LOW	libqpdf/sph/sph_types.h	1041	#ifdef __GNUC__	COMMENT
LOW	libqpdf/sph/sph_types.h	1101	#define SPH_DETECT_BIG_ENDIAN 1	COMMENT
LOW	libqpdf/sph/sph_types.h	1121	#endif	COMMENT
LOW	libqpdf/sph/sph_types.h	1141	#if defined SPH_DETECT_LITTLE_FAST && !defined SPH_LITTLE_FAST	COMMENT
LOW	libqpdf/sph/sph_types.h	1161	#endif	COMMENT
LOW	libqpdf/sph/sph_types.h	1981	# pragma GCC diagnostic pop	COMMENT
LOW	libqpdf/qpdf/assert_debug.h	1	/*	COMMENT
LOW	libqpdf/qpdf/rijndael.h	21	#define KEYLENGTH(keybits) ((keybits) / 8)	COMMENT
LOW	include/qpdf/DLL.h	41	* binary interface). See below for a detailed explanation.	COMMENT
LOW	qtest/module/TestDriver.pm	1	# -- perl --	COMMENT
LOW	qtest/module/TestDriver.pm	381	# PUBLIC METHODS	COMMENT
LOW	qtest/module/TestDriver.pm	501	# description: a short textual description of the test case	COMMENT
LOW	qtest/module/TestDriver.pm	521		COMMENT
LOW	qtest/module/TestDriver.pm	541	# environment.	COMMENT
LOW	qtest/module/TestDriver.pm	561	# through any filter. Newlines are also normalized in the	COMMENT
LOW	qtest/module/TestDriver.pm	1761	}	COMMENT
LOW	qtest/module/TestDriver.pm	1781	# * Pipes work unreliably. Fork emulation is very incomplete.	COMMENT
LOW	qtest/module/TestDriver.pm	1861	# END OF TestDriver	COMMENT

Self-Referential Comments1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	qtest/module/TestDriver.pm	3	# This file is part of qtest.	COMMENT

Redundant / Tautological Comments1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	qtest/module/TestDriver.pm	792	# Open file handle into which to write the actual output	COMMENT

AI Slop Vocabulary1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	qtest/module/TestDriver.pm	1234	# It doesn't work to just call <$fh> in this case. For some	COMMENT

Unused Imports1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	manual/conf.py	9		CODE