AI Slop Code Risk Monitor

Yamato-Security/hayabusa

Name: Yamato-Security/hayabusa — Rust 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).

Hayabusa (隼) is a sigma-based threat hunting and fast forensics timeline generator for Windows event logs.

0.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for Yamato-Security/hayabusa, a Rust project with 3,427 GitHub stars. SynthScan examined 140,711 lines of code across 691 source files, recording 25 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 0.3 (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.

0.3

Adjusted Signal

0.3

Raw Pattern Score

100%

Time Factor

2026-10-28

Last Push

3.4K

Stars

Rust

Language

140.7K

Lines of Code

691

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

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 0.5/100 · LOW

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

PR Review Velocity Impact 1.1/100 · LOW

Which changes need focused human review? 25 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 3LOW 22

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 25 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 Block19 hits · 19 pts

Severity	File	Line	Snippet	Context
LOW	art/takoyaki.txt	1		COMMENT
LOW	art/takoyaki.txt	21	########((((####.(##########(*(((#,##..#	COMMENT
LOW	website/mkdocs.yml	1	# =============================================================================	COMMENT
LOW	.github/workflows/release.yml	101	- name: Install aarch64-unknown-linux-musl toolchain	COMMENT
LOW	.github/workflows/rust.yml	21	# platform matrix still runs in release.yml. Uncomment the entries below to	COMMENT
LOW	src/main.rs	161	/// and `main` then ends normally — used to leave the exit status at 0. A script or CI job	COMMENT
LOW	src/yaml_expand.rs	41	.iter()	COMMENT
LOW	src/results/json.rs	161	.prev_details_convert_map	COMMENT
LOW	src/results/mod.rs	21	/// HTML special characters are entity-escaped (stops raw-HTML injection like	COMMENT
LOW	src/results/mod.rs	421	.collect();	COMMENT
LOW	src/detections/configs.rs	141	pub output_option: Option<OutputOption>,	COMMENT
LOW	src/detections/configs.rs	2021	impl ConfigReader {	COMMENT
LOW	src/detections/utils.rs	961	/// verified against the full sample-evtx corpus, where CSV output stays byte-identical and JSON	COMMENT
LOW	src/detections/rule/rulenode.rs	21	RuleNode::new(rule_path, yaml)	COMMENT
LOW	src/detections/rule/correlation_parser.rs	361	};	COMMENT
LOW	src/detections/rule/matchers/mod.rs	21	pub use crate::detections::rule::fast_match::FastMatch;	COMMENT
LOW	src/detections/rule/matchers/default_matcher.rs	101	// module and are imported above.	COMMENT
LOW	src/timeline/metrics.rs	41		COMMENT
LOW	src/timeline/sort_csv.rs	141	/// Order `rows` by `key_of` and keep only the first of any set of rows that are identical apart	COMMENT

Decorative Section Separators3 hits · 14 pts

Severity	File	Line	Snippet	Context
MEDIUM⚡	website/mkdocs.yml	1	# =============================================================================	COMMENT
MEDIUM⚡	website/mkdocs.yml	3	# -----------------------------------------------------------------------------	COMMENT
MEDIUM⚡	website/mkdocs.yml	9	# =============================================================================	COMMENT

Fake / Example Data3 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	website/docs/rules/sigma-curation.es.md	246	2. Las reglas de tipo "placeholder" (marcador de posición) se ignoran porque no se pueden usar tal cual. Se trata de reg	CODE
LOW	website/docs/rules/sigma-curation.pt-BR.md	246	2. Regras "placeholder" são ignoradas porque não podem ser usadas como estão. São regras colocadas na pasta [`rules-plac	CODE
LOW	website/docs/rules/sigma-curation.id.md	246	2. Aturan "placeholder" diabaikan karena tidak dapat digunakan apa adanya. Ini adalah aturan yang ditempatkan dalam fold	CODE