AI Slop Code Risk Monitor

FareedKhan-dev/kimi-k3-in-c

Name: FareedKhan-dev/kimi-k3-in-c — 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).

A 2.78-trillion-parameter Kimi K3 running inference on a single CPU in 8.24 GB of RAM. Portable C99: no BLAS, no framework, no GPU.

2.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for FareedKhan-dev/kimi-k3-in-c, a C project with 9,269 GitHub stars. SynthScan examined 31,497 lines of code across 124 source files, recording 58 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 2.1 (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.1

Adjusted Signal

2.1

Raw Pattern Score

100%

Time Factor

2026-10-02

Last Push

9.3K

Stars

Language

31.5K

Lines of Code

124

Files

Pattern Hits

2026-10-31

Scan Date

0.01

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

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

Hallucinated Dependency & Supply Chain Risk 4.3/100 · LOW

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

Agent Over-Engineering Ratio 1.3/100 · LOW

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

PR Review Velocity Impact 10.1/100 · LOW

Which changes need focused human review? 58 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 1MEDIUM 2LOW 55

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 58 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.

Unused Imports23 hits · 23 pts

Severity	File	Line	Context
LOW	tools/devbw.py	19	CODE
LOW	tools/make_tiny_checkpoint.py	26	CODE
LOW	tools/k3_ref.py	77	CODE
LOW	tools/make_cache_fixture.py	30	CODE
LOW	tools/make_st_fixture.py	19	CODE
LOW	tools/sim_cache.py	24	CODE
LOW	tools/cmp_logits.py	24	CODE
LOW	tools/budget.py	32	CODE
LOW	tools/verify_mla.py	32	CODE
LOW	tools/_paths.py	29	CODE
LOW	tools/conform_all.py	32	CODE
LOW	tools/verify_st.py	22	CODE
LOW	tools/emit_fixtures.py	49	CODE
LOW	tools/layers_to_shards.py	26	CODE
LOW	tools/tok.py	19	CODE
LOW	tools/make_k3_oracle.py	44	CODE
LOW	tools/verify_real_layer.py	30	CODE
LOW	tools/ref_forward.py	36	CODE
LOW	tools/pack_trunk.py	27	CODE
LOW	tools/verify_kda.py	35	CODE
LOW	tools/verify_expert.py	28	CODE
LOW	tools/tok_parity.py	17	CODE
LOW	docs/images/_plots.py	25	CODE

Over-Commented Block15 hits · 15 pts

Severity	File	Line	Snippet	Context
LOW	tools/make_tiny_checkpoint.py	101	# 2^0 the smallest scale, so the smallest representable non-zero magnitude is 0.5 *	COMMENT
LOW	tools/ref_forward.py	61	# WHAT IS DELIBERATELY NOT QUANTISED, and why:	COMMENT
LOW	tests/unit/test_trunk.c	41	#include "k3_portable_io.h" /* first: establishes Darwin feature macros */	COMMENT
LOW	examples/03-long-prompt.sh	1	#!/usr/bin/env bash	COMMENT
LOW	benchmarks/split-sweep.sh	1	#!/usr/bin/env bash	COMMENT
LOW	benchmarks/memory-ladder.sh	1	#!/usr/bin/env bash	COMMENT
LOW	scripts/k3-doctor.sh	1	#!/usr/bin/env bash	COMMENT
LOW	scripts/download-model.sh	1	#!/usr/bin/env bash	COMMENT
LOW	scripts/download-model.sh	81		COMMENT
LOW	scripts/pack-trunk.sh	1	#!/usr/bin/env bash	COMMENT
LOW	src/io/k3_trunk.c	1	/* k3_trunk.c - see k3_trunk.h for why the trunk is streamed rather than quantised. */	COMMENT
LOW	src/io/k3_portable_io.h	101	{	COMMENT
LOW	src/cli/k3_sysmem.h	21	* Both functions return 0 when the platform cannot say, which every caller already	COMMENT
LOW	src/cli/k3_run.c	41	/* _POSIX_C_SOURCE alone hides the BSD rusage fields, ru_maxrss among them, from	COMMENT
LOW	src/cli/k3_run.c	61	#endif	COMMENT

Deep Nesting9 hits · 9 pts

Severity	File	Line	Context
LOW	tools/devbw.py	41	CODE
LOW	tools/devbw.py	47	CODE
LOW	tools/make_tiny_checkpoint.py	198	CODE
LOW	tools/make_tiny_checkpoint.py	234	CODE
LOW	tools/budget.py	101	CODE
LOW	tools/conform_all.py	44	CODE
LOW	tools/tok.py	196	CODE
LOW	tools/make_k3_oracle.py	60	CODE
LOW	tools/pack_trunk.py	46	CODE

Excessive Try-Catch Wrapping8 hits · 8 pts

Severity	File	Line	Snippet	Context
LOW	tools/devbw.py	62	except Exception as e:	CODE
LOW	tools/devbw.py	88	except Exception as e:	CODE
LOW	tools/cmp_logits.py	73	except Exception:	CODE
LOW	tools/verify_mla.py	68	except Exception as e:	CODE
LOW	tools/verify_kda.py	78	except Exception as e:	CODE
LOW	docs/images/_eq.py	224	except Exception as e:	CODE
LOW	docs/images/_plots.py	923	except Exception as e:	CODE
LOW	scripts/download-model.sh	111	except Exception:	CODE

AI Slop Vocabulary2 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	tools/verify_mla.py	123	# look like a model bug when it is purely a harness artefact.	COMMENT
MEDIUM	benchmarks/memory-ladder.sh	106	# The determinism assertion is the entire point of this harness, so it must not	COMMENT

Cross-Language Confusion1 hit · 5 pts

Severity	File	Line	Snippet	Context
HIGH	tools/tok_parity.py	73	("json", '{"key": [1, 2, {"n": null}], "b": true}'),	CODE