AI Slop Code Risk Monitor

lldap/lldap

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

Light LDAP implementation

1.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for lldap/lldap, a Rust project with 6,605 GitHub stars. SynthScan examined 40,465 lines of code across 301 source files, recording 39 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.3

Adjusted Signal

1.3

Raw Pattern Score

100%

Time Factor

2026-09-26

Last Push

6.6K

Stars

Rust

Language

40.5K

Lines of Code

301

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

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

Are imports declared and package/API names verified? 3 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.9/100 · LOW

Which changes need focused human review? 39 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 38

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 39 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 Block24 hits · 24 pts

Severity	File	Line	Snippet	Context
LOW	lldap_config.docker_template.toml	1	## Default configuration for Docker.	COMMENT
LOW	lldap_config.docker_template.toml	21		COMMENT
LOW	lldap_config.docker_template.toml	41	## Random secret for JWT signature.	COMMENT
LOW	lldap_config.docker_template.toml	61	#ldap_base_dn = "dc=example,dc=com"	COMMENT
LOW	lldap_config.docker_template.toml	81	## in the LLDAP_LDAP_USER_PASS_FILE environment variable	COMMENT
LOW	lldap_config.docker_template.toml	101	## - "mysql://mysql-user:password@mysql-server/my-database"	COMMENT
LOW	lldap_config.docker_template.toml	121		COMMENT
LOW	lldap_config.docker_template.toml	141	#smtp_encryption = "TLS"	COMMENT
LOW	lldap_config.docker_template.toml	161	#cert_file="/data/cert.pem"	COMMENT
LOW	crates/graphql-server/Cargo.toml	61	path = "../test-utils"	COMMENT
LOW	crates/graphql-server/src/mutation/inputs.rs	1	use juniper::{GraphQLInputObject, GraphQLObject};	COMMENT
LOW	crates/graphql-server/src/mutation/inputs.rs	61	/// Attribute names to remove.	COMMENT
LOW	app/src/infra/common_component.rs	1	//! Common Component module.	COMMENT
LOW	server/src/configuration.rs	101	#[derive(Clone, Deserialize, Serialize, derive_more::Debug)]	COMMENT
LOW	server/src/cli.rs	81	#[clap(subcommand)]	COMMENT
LOW	server/src/cli.rs	121	#[derive(Debug, Parser, Clone)]	COMMENT
LOW	.github/workflows/docker-build-static.yml	41	# Using lldap dev image based on https://hub.docker.com/_/rust and musl-gcc bundled #	COMMENT
LOW	.github/workflows/docker-build-static.yml	561	with:	COMMENT
LOW	.github/workflows/docker-build-static.yml	601	# vX-alpine	COMMENT
LOW	example_configs/authelia.md	21	# Set base dn that you configured in LLDAP	COMMENT
LOW	example_configs/lldap-ha-auth.sh	1	#!/bin/bash	COMMENT
LOW	example_configs/home-assistant.md	21	# <regular user group>: Find users that has permission to access homeassistant, anyone inside	COMMENT
LOW	example_configs/grafana_ldap_config.toml	1	# This is only the ldap config, you also need to enable ldap support in the main config file	COMMENT
LOW	example_configs/grafana_ldap_config.toml	41	surname = "sn"	COMMENT

Structural Annotation Overuse10 hits · 20 pts

Severity	File	Line	Snippet	Context
LOW⚡	docs/migration_guides/v0.5.md	17	### Step 1: Take a note of the users with duplicate emails	COMMENT
LOW⚡	docs/migration_guides/v0.5.md	22	### Step 2: Downgrade to v0.4.3	COMMENT
LOW⚡	docs/migration_guides/v0.5.md	29	### Step 3: Remove duplicate emails	COMMENT
LOW⚡	docs/migration_guides/v0.5.md	34	### Step 4: Upgrade again	COMMENT
LOW	example_configs/truenas-install.md	14	## Step 1: Install LLDAP from the TrueNAS Apps Catalog	COMMENT
LOW	example_configs/truenas-install.md	23	## Step 2: Application Configuration	COMMENT
LOW	example_configs/truenas-install.md	62	## Step 3: Storage Configuration	COMMENT
LOW⚡	example_configs/truenas-install.md	79	## Step 5: Deploy the App	COMMENT
LOW⚡	example_configs/truenas-install.md	85	## Step 6: Access the LLDAP Web UI	COMMENT
LOW⚡	example_configs/truenas-install.md	95	## Step 7: Using LLDAP with Other Applications	COMMENT

Fake / Example Data3 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	lldap_config.docker_template.toml	72	#ldap_user_email = "admin@example.com"	COMMENT
LOW	crates/sql-backend-handler/src/sql_tables.rs	257	VALUES ("john", "John Doe", "John", "1971-01-01 00:00:00", "bob2@bob.com")"#,	CODE
LOW	crates/sql-backend-handler/src/sql_tables.rs	300	display_name: Some("John Doe".to_owned()),	CODE

Slop Phrases1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	lldap_config.docker_template.toml	125	## to ignore the attribute and the service works without, you can add it to this	COMMENT

Redundant / Tautological Comments1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	scripts/bootstrap.sh	481	# Check if value is a JSON array	COMMENT