AI Slop Code Risk Monitor

QuipNetwork/hashsigs-solidity

Name: QuipNetwork/hashsigs-solidity — Solidity 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).

Solidity contracts implementing hash based post quantum signatures

1.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for QuipNetwork/hashsigs-solidity, a Solidity project with 11,204 GitHub stars. SynthScan examined 14,146 lines of code across 42 source files, recording 16 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.7 (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.7

Adjusted Signal

1.7

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

11.2K

Stars

Solidity

Language

14.1K

Lines of Code

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

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

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

PR Review Velocity Impact 8.1/100 · LOW

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

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 16 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 Block12 hits · 12 pts

Severity	File	Line	Snippet	Context
LOW	foundry.toml	21	# Suppress solc warning 2018 ("state mutability can be restricted to pure")	COMMENT
LOW	foundry.toml	41	# Profile selection ([DESIGN §3.4]): the `shrincs-profile/` prefix	COMMENT
LOW	foundry.toml	81	# The next three read grants (contracts/, script/, docs/) have no	COMMENT
LOW	foundry.toml	101		COMMENT
LOW	foundry.toml	261	# under the sha2 suite the signer swaps to SHA-256 in lockstep with the	COMMENT
LOW	foundry.toml	281	"contracts/SHRINCS128sQ18Keccak.sol",	COMMENT
LOW	foundry.toml	301	# Measurements and StatelessDelegation no longer import a concrete	COMMENT
LOW	.gitlab-ci.yml	61	# params (inherited from default) plus bounded, deterministic	COMMENT
LOW	.gitlab-ci.yml	81	- forge lint --deny warnings contracts/ test/ script/	COMMENT
LOW	.gitlab-ci.yml	141	# profile's test set, whose failure dirs are the cache/fuzz +	COMMENT
LOW	scripts/gas-report.sh	1	#!/usr/bin/env bash	COMMENT
LOW	scripts/check-line-length.sh	1	#!/bin/sh	COMMENT

AI Slop Vocabulary2 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	foundry.toml	90	# (task 1vn) selects its profile-gated harness contracts (e.g.	COMMENT
MEDIUM	.gitlab-ci.yml	190	# Medusa v1.5.1 coverage-guided campaign over the state-machine harness	COMMENT

Decorative Section Separators2 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	.gitlab-ci.yml	132	# ---------------------------------------------------------------------------	COMMENT
MEDIUM	.gitlab-ci.yml	151	# ---------------------------------------------------------------------------	COMMENT