AI Slop Code Risk Monitor

bee-san/Ciphey

SlopCodeMonitor badge for bee-san/Ciphey Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

⚡ Automatically decrypt encryptions without knowing the key or cipher, decode encodings, and crack hashes ⚡

2.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for bee-san/Ciphey, a Rust project with 21,730 GitHub stars. SynthScan examined 181,284 lines of code across 290 source files, recording 430 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 2.4 (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.4
Adjusted Signal
2.4
Raw Pattern Score
100%
Time Factor
2026-10-28
Last Push
21.7K
Stars
Rust
Language
181.3K
Lines of Code
290
Files
430
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 10.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 11.5/100 · LOW

Which changes need focused human review? 430 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 7LOW 423

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 430 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 Block410 hits · 396 pts
SeverityFileLineSnippetContext
LOWimages/repomix-output.txt101#COMMENT
LOWimages/repomix-output.txt121# Set PlaybackSpeed <float> Set the playback speed of the recordingCOMMENT
LOWimages/repomix-output.txt141# Down[@<time>] [number] Press the Down keyCOMMENT
LOWimages/repomix-output.txt181# Require <string> Ensure a program is on the $PATH to proceedCOMMENT
LOWimages/repomix-output.txt201#COMMENT
LOWtests/standard_galactic_alphabet_decoder.rs1//! End-to-end tests for the Standard Galactic Alphabet decoderCOMMENT
LOWtests/standard_galactic_alphabet_decoder.rs21/// The plaintext of the bench fixturesCOMMENT
LOWtests/base36_decoder.rs1//! End-to-end tests for the Base36 decoder (<https://github.com/bee-san/Ciphey/issues/922>):COMMENT
LOWtests/multi_tap_decoder.rs1//! End-to-end tests for the Multi-tap decoder (<https://github.com/bee-san/Ciphey/issues/960>):COMMENT
LOWtests/backslash_escape_decoder.rs1//! End-to-end tests for the Backslash Escapes decoderCOMMENT
LOWtests/punycode_decoder.rs1//! End-to-end tests for the Punycode decoder (<https://github.com/bee-san/Ciphey/issues/938>):COMMENT
LOWtests/plaintext_detection.rs1//! The 20 end-to-end cases from <https://github.com/bee-san/Ciphey/issues/1031>, run the wayCOMMENT
LOWtests/baudot_decoder.rs1//! End-to-end tests for the Baudot decoder (<https://github.com/bee-san/Ciphey/issues/956>):COMMENT
LOWtests/core_socialist_values_decoder.rs1//! End-to-end tests for the Core Socialist Values decoderCOMMENT
LOWtests/hill_decoder_crib.rs1//! End-to-end test for the Hill cracker (<https://github.com/bee-san/Ciphey/issues/1011>)COMMENT
LOWtests/vigenere_autokey_crib.rs1//! End-to-end test for the Vigenère autokey crackerCOMMENT
LOWtests/unicode_fancy_text_decoder.rs1//! End-to-end tests for the Unicode Fancy Text decoderCOMMENT
LOWtests/keyboard_layout_decoder.rs1//! End-to-end tests for the Keyboard layout decoderCOMMENT
LOWtests/ascii_shift_decoder.rs1//! End-to-end tests for the ASCII shift cracker (<https://github.com/bee-san/Ciphey/issues/994>):COMMENT
LOWtests/rot18_decoder.rs1//! End-to-end tests for the ROT5 / ROT18 crackerCOMMENT
LOWtests/nato_phonetic_decoder_crib.rs1//! End-to-end tests for the NATO phonetic alphabet decoderCOMMENT
LOWtests/hill_decoder.rs1//! End-to-end tests for the Hill cracker (<https://github.com/bee-san/Ciphey/issues/1011>):COMMENT
LOWtests/aaencode_decoder.rs1//! End-to-end tests for the AAEncode decoder (<https://github.com/bee-san/Ciphey/issues/988>):COMMENT
LOWtests/ascii_shift_crib.rs1//! End-to-end test for the ASCII shift cracker (<https://github.com/bee-san/Ciphey/issues/994>)COMMENT
LOWtests/polybius_decoder.rs1//! End-to-end tests for the Polybius Square decoderCOMMENT
LOWtests/jsfuck_decoder_crib.rs1//! End-to-end test for the JSFuck decoder (<https://github.com/bee-san/Ciphey/issues/987>)COMMENT
LOWtests/yunying_decoder.rs1//! End-to-end tests for the 01248 (Yunying) decoderCOMMENT
LOWtests/dna_codon_decoder.rs1//! End-to-end tests for the DNA Codon decoder (<https://github.com/bee-san/Ciphey/issues/966>):COMMENT
LOWtests/tap_code_decoder.rs1//! End-to-end tests for the Tap Code decoder (<https://github.com/bee-san/Ciphey/issues/962>):COMMENT
LOWtests/zero_width_crib.rs1//! End-to-end tests for the Zero-width decoderCOMMENT
LOWtests/route_transposition_decoder.rs1//! End-to-end tests for the Route Transposition decoderCOMMENT
LOWtests/ctf_corpus.rs1//! Real CTF strings, run through the full search.COMMENT
LOWtests/big_integer_decoder.rs1//! End-to-end tests for the Big integer to bytes decoderCOMMENT
LOWtests/zero_width_decoder.rs1//! End-to-end tests for the Zero-width decoderCOMMENT
LOWtests/nato_phonetic_decoder.rs1//! End-to-end tests for the NATO phonetic alphabet decoderCOMMENT
LOWtests/leetspeak_decoder.rs1//! End-to-end tests for the Leetspeak decoder (<https://github.com/bee-san/Ciphey/issues/969>):COMMENT
LOWtests/keyboard_shift_decoder.rs1//! End-to-end tests for the Keyboard shift decoder (<https://github.com/bee-san/Ciphey/issues/976>):COMMENT
LOWtests/base92_decoder.rs1//! End-to-end tests for the Base92 decoder (<https://github.com/bee-san/Ciphey/issues/927>):COMMENT
LOWtests/test_fixtures/jsfuck.toml1# JSFuck test vectors for src/decoders/jsfuck_decoder.rs and tests/jsfuck_decoder.rs.COMMENT
LOWdocs/wordlist.md141COMMENT
LOWdocs/wordlist.md161/// 1. Memory mapping (unsafe { Mmap::map(&file) }):COMMENT
LOWdocs/changes/wordlist.md141COMMENT
LOWdocs/changes/wordlist.md161/// 1. Memory mapping (unsafe { Mmap::map(&file) }):COMMENT
LOW.github/workflows/release.yml1# Copyright 2022-2023, axodotdevCOMMENT
LOW.github/workflows/release.yml21 contents: writeCOMMENT
LOWbenches/plaintext.rs1//! Plaintext-detection benchmark: how well the checkers tell plaintext from the junk aCOMMENT
LOWbenches/plaintext.rs21//!COMMENT
LOWbenches/decoders.rs1//! Every decoder on realistic input.COMMENT
LOWbenches/startup.rs1//! Startup and per-call overhead outside the search itself.COMMENT
LOWbenches/search.rs1//! The A* search end to end, through `ciphey::perform_cracking`, on the corpus inCOMMENT
LOWbenches/data/decoders.toml1# Decoder benchmark fixtures (used by benches/decoders.rs).COMMENT
LOWbenches/data/decoders.toml21# success = whether Decoder::crack reports success with the Athena checker todayCOMMENT
LOWbenches/data/checkers.toml1# Checker benchmark fixtures (used by benches/checkers.rs and benches/crib.rs).COMMENT
LOWbenches/data/search.toml1# A* search corpus (used by benches/search.rs), run end to end throughCOMMENT
LOWsrc/error.rs1use thiserror::Error;COMMENT
LOWsrc/lib.rs1//! ciphey is an automatic decoding and cracking tool. <https://github.com/bee-san/ciphey>COMMENT
LOWsrc/lib.rs41/// ```COMMENT
LOWsrc/lib.rs101/// // You can set the config to your liking using the Config structCOMMENT
LOWsrc/lib.rs121/// let mut config = Config::default();COMMENT
LOWsrc/detection.rs1//! Plaintext detection: is a text plaintext, and what is it?COMMENT
350 more matches not shown…
Fake / Example Data12 hits · 13 pts
SeverityFileLineSnippetContext
LOWtests/integration_test.rs458const JWT_IO_PAYLOAD: &str = r#"{"sub":"1234567890","name":"John Doe","iat":1516239022}"#;CODE
LOWtests/cli.rs407 .contains(r#"{"sub":"1234567890","name":"John Doe","iat":1516239022}"#),CODE
LOWsrc/decoders/dtmf_decoder.rs678 assert_eq!(crack("555-1234"), None);CODE
LOWsrc/decoders/jwt_decoder.rs56/// r#"{"sub":"1234567890","name":"John Doe","iat":1516239022}"#COMMENT
LOWsrc/decoders/jwt_decoder.rs323 const JWT_IO_PAYLOAD: &str = r#"{"sub":"1234567890","name":"John Doe","iat":1516239022}"#;CODE
LOWsrc/decoders/brainfuck_interpreter.rs151 "Lorem Ipsum! Oh, Happy Day! Hello World! I hope you have a lovely day!"CODE
LOWsrc/decoders/keyboard_layout_decoder.rs867 "Lorem ipsum dolor sit amet, consectetur adipiscing elit",CODE
LOWsrc/decoders/keyboard_layout_decoder.rs867 "Lorem ipsum dolor sit amet, consectetur adipiscing elit",CODE
LOWsrc/decoders/affine_decoder.rs678 "Lorem ipsum dolor sit amet, consectetur adipiscing elit",CODE
LOWsrc/decoders/affine_decoder.rs678 "Lorem ipsum dolor sit amet, consectetur adipiscing elit",CODE
LOWsrc/decoders/leetspeak_decoder.rs818 "user@example.com",CODE
LOWsrc/decoders/api/functions.rs563 /// assert_eq!(payload.text, r#"{"sub":"1234567890","name":"John Doe","iat":1516239022}"#);COMMENT
AI Slop Vocabulary5 hits · 13 pts
SeverityFileLineSnippetContext
MEDIUMsrc/checkers/english.rs81/// strictest). Chosen with the #1031 harness so that the issue's corpusCOMMENT
MEDIUMsrc/checkers/english.rs963 // Wrong-key Vigenère outputs from the #1031 harnessCOMMENT
MEDIUMsrc/storage/ngrams/generate.py236 `category<TAB>split<TAB>text` lines. Pride and Prejudice's are the 200 lines the #1031 harnessSTRING
MEDIUMsrc/decoders/vigenere_decoder.rs112/// English words. In the #1031 harness the right key's output never scoresCOMMENT
MEDIUMsrc/decoders/quoted_printable_decoder.rs235 // RFC 2045 §6.7 note 1: a robust decoder accepts lowercase hexCOMMENT
Self-Referential Comments2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/release.yml48 # Create the Github Release™ so the packages have something to be uploaded toCOMMENT
MEDIUM.github/workflows/release.yml67 # Create the Github Release™ based on what cargo-dist thinks it should beCOMMENT
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWsrc/storage/ngrams/generate.py256CODE