AI Slop Code Risk Monitor

agenda/agenda

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

Lightweight job scheduling for Node.js

0.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for agenda/agenda, a HTML project with 9,712 GitHub stars. SynthScan examined 101,174 lines of code across 277 source files, recording 39 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 0.5 (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.5

Adjusted Signal

0.5

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

9.7K

Stars

HTML

Language

101.2K

Lines of Code

277

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

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

Hallucinated Dependency & Supply Chain Risk 0.6/100 · LOW

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

Agent Over-Engineering Ratio 0.4/100 · LOW

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

PR Review Velocity Impact 2.0/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 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.

Structural Annotation Overuse10 hits · 17 pts

Severity	File	Line	Snippet	Context
LOW	docs/migration-guide-v6.md	458	### Step 1: Update Node.js	COMMENT
LOW	docs/migration-guide-v6.md	465	### Step 2: Install Packages	COMMENT
LOW	docs/migration-guide-v6.md	476	### Step 3: Update Imports	COMMENT
LOW	docs/migration-guide-v6.md	498	### Step 4: Update Agenda Instantiation	COMMENT
LOW	docs/migration-guide-v6.md	519	### Step 5: Move Backend-Specific Options	COMMENT
LOW	docs/migration-guide-v6.md	541	### Step 6: Update Custom Repository Usage	COMMENT
LOW	docs/migration-guide-v6.md	570	### Step 7: Update Tests	COMMENT
LOW⚡	packages/agenda/src/utils/dateConstraints.ts	136	// Step 1: Apply date range constraints (start date)	COMMENT
LOW⚡	packages/agenda/src/utils/dateConstraints.ts	142	// Step 2: Apply skip days	COMMENT
LOW⚡	packages/agenda/src/utils/dateConstraints.ts	148	// Step 3: Check end date constraint again (skip days may have moved the date)	COMMENT

Fake / Example Data12 hits · 12 pts

Severity	File	Line	Snippet	Context
LOW	README.md	154	await agenda.schedule('in 20 minutes', 'send email report', { to: 'admin@example.com' });	CODE
LOW	docs/migration-guide-v6.md	612	await agenda.every('1 hour', 'send-email', { to: 'user@example.com', subject: 'Hello' });	CODE
LOW	docs/migration-guide-v6.md	643	await agenda.every('1 hour', 'send-email', { to: 'user@example.com', subject: 'Hello' });	CODE
LOW	examples/decorators.ts	214	recipient: 'admin@example.com',	CODE
LOW	examples/job-data-types.ts	122	to: 'user@example.com',	CODE
LOW	examples/job-data-types.ts	137	street: '123 Main St',	CODE
LOW	examples/job-data-types.ts	160	to: 'admin@example.com',	CODE
LOW	packages/redis-backend/README.md	49	await agenda.every('5 minutes', 'send-email', { to: 'user@example.com', subject: 'Hello', body: 'World' });	CODE
LOW	packages/agenda/README.md	78	await agenda.every('1 hour', 'send email', { to: 'user@example.com', subject: 'Hello' });	CODE
LOW	packages/agenda/README.md	79	await agenda.schedule('in 5 minutes', 'send email', { to: 'admin@example.com', subject: 'Report' });	CODE
LOW	packages/mongo-backend/README.md	52	await agenda.every('1 hour', 'send-email', { to: 'user@example.com', subject: 'Hello' });	CODE
LOW	packages/postgres-backend/README.md	48	await agenda.every('5 minutes', 'send-email', { to: 'user@example.com', subject: 'Hello', body: 'World' });	CODE

Hyper-Verbose Identifiers8 hits · 8 pts

Severity	File	Line	Snippet	Context
LOW	…ages/agenda/test/shared/removeoncomplete-test-suite.ts	39	export function removeOnCompleteTestSuite(config: RemoveOnCompleteTestConfig): void {	CODE
LOW	…/agenda/test/shared/notification-channel-test-suite.ts	57	function createTestStateNotification(	CODE
LOW	…/agenda/test/shared/notification-channel-test-suite.ts	73	export function notificationChannelTestSuite(config: NotificationChannelTestConfig): void {	CODE
LOW	packages/agenda/src/decorators/metadata.ts	52	export function getOrCreateControllerMetadata(target: Constructor): ControllerMetadata {	CODE
LOW	packages/agenda/src/decorators/metadata.ts	52	export function getOrCreateControllerMetadata(target: Constructor): ControllerMetadata {	CODE
LOW	packages/agenda/src/utils/dateConstraints.ts	96	export function applyDateRangeConstraints(	CODE
LOW	packages/agendash/client/src/App.vue	134	function handleConfirmRequeueMulti(jobIds: string[]) {	CODE
LOW	packages/postgres-backend/src/schema.ts	78	export function getUpdateTimestampTriggerSQL(tableName: string): string {	CODE

Verbosity Indicators3 hits · 7 pts

Severity	File	Line	Snippet	Context
LOW⚡	packages/agenda/src/utils/dateConstraints.ts	136	// Step 1: Apply date range constraints (start date)	COMMENT
LOW⚡	packages/agenda/src/utils/dateConstraints.ts	142	// Step 2: Apply skip days	COMMENT
LOW⚡	packages/agenda/src/utils/dateConstraints.ts	148	// Step 3: Check end date constraint again (skip days may have moved the date)	COMMENT

Slop Phrases2 hits · 4 pts

Severity	File	Line	Snippet	Context
MEDIUM	eslint.config.js	49	// Examples are allowed to use console for demonstration purposes	COMMENT
LOW	docs-legacy/4.x/index.html	668	<p><em>IMPORTANT:</em> To <a href="https://docs.mongodb.com/manual/reference/method/db.collection.update/#use-unique-ind	CODE

Over-Commented Block4 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	examples/graceful-shutdown.ts	81		COMMENT
LOW	examples/graceful-shutdown.ts	101	// ALTERNATIVE: Shutdown with timeout	COMMENT
LOW	.github/workflows/codeql-analysis.yml	1	# For most projects, this workflow file will not need changing; you simply need	COMMENT
LOW	.github/workflows/codeql-analysis.yml	61	# ℹ️ Command-line programs to run using the OS shell.	COMMENT