AI Slop Code Risk Monitor

rajnandan1/kener

SlopCodeMonitor badge for rajnandan1/kener Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Stunning status pages, batteries included!

1.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for rajnandan1/kener, a TypeScript project with 5,234 GitHub stars. SynthScan examined 128,264 lines of code across 1075 source files, recording 115 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 1.7 (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.7
Adjusted Signal
1.7
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
5.2K
Stars
TypeScript
Language
128.3K
Lines of Code
1.1K
Files
115
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 3.9/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.7/100 · LOW

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

Agent Over-Engineering Ratio 4.8/100 · LOW

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

PR Review Velocity Impact 7.2/100 · LOW

Which changes need focused human review? 115 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 8MEDIUM 19LOW 88

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 115 distinct pattern matches across 8 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.

Decorative Section Separators18 hits · 69 pts
SeverityFileLineSnippetContext
MEDIUM⚡docker-compose.dev.yml1# =============================================================================COMMENT
MEDIUM⚡docker-compose.dev.yml12# =============================================================================COMMENT
MEDIUM⚡docker-compose.dev.yml15 # ---------------------------------------------------------------------------COMMENT
MEDIUM⚡docker-compose.dev.yml17 # ---------------------------------------------------------------------------COMMENT
MEDIUMdocker-compose.dev.yml29 # ---------------------------------------------------------------------------COMMENT
MEDIUMdocker-compose.dev.yml31 # ---------------------------------------------------------------------------COMMENT
MEDIUM⚡docker-compose.status.yml1# =============================================================================COMMENT
MEDIUM⚡docker-compose.status.yml6# =============================================================================COMMENT
MEDIUM⚡docker-compose.yml1# =============================================================================COMMENT
MEDIUM⚡docker-compose.yml9# =============================================================================COMMENT
MEDIUM⚡docker-compose.yml12 # ---------------------------------------------------------------------------COMMENT
MEDIUM⚡docker-compose.yml14 # ---------------------------------------------------------------------------COMMENT
MEDIUMdocker-compose.yml27 # ---------------------------------------------------------------------------COMMENT
MEDIUMdocker-compose.yml29 # ---------------------------------------------------------------------------COMMENT
MEDIUMdocker-compose.yml68 # ---------------------------------------------------------------------------COMMENT
MEDIUMdocker-compose.yml70 # ---------------------------------------------------------------------------COMMENT
MEDIUMdocker-compose.yml87 # ---------------------------------------------------------------------------COMMENT
MEDIUMdocker-compose.yml89 # ---------------------------------------------------------------------------COMMENT
Hyper-Verbose Identifiers54 hits · 58 pts
SeverityFileLineSnippetContext
LOWscripts/sort-translations.js28function replaceMappingsPreserveTopLevelOrder(localeData, sortedMappings) {CODE
LOWsrc/lib/clientTools.ts430function ResolveEventListPlacement(settings: Partial<EventDisplaySettings> | null | undefined): EventListPlacement {CODE
LOWsrc/lib/server/redisConnector.ts10function shouldReconnectAfterRedisError(message: string): boolean {CODE
LOWsrc/lib/server/tool.ts128function GetWordsStartingWithDollar(text: string): string[] {CODE
LOWsrc/lib/server/pageSettings.ts158function sanitizeStoredMaintenances(value: unknown): PageSettingsPatch["include_maintenances"] {CODE
LOWsrc/lib/server/rss.ts220function buildMaintenanceDescription(maintenance: MaintenanceEventsMonitorList): string {CODE
LOWsrc/lib/server/notification/notification_utils.ts52function formatMaintenanceMarkdown(CODE
LOWsrc/lib/server/db/repositories/monitors.ts10function clampConfirmationThreshold(value: number | null | undefined): number {CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts88function validateMonitorAlertConfigInput(data: MonitorAlertConfigCreateInput | MonitorAlertConfigUpdateInput): void {CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts252export async function ToggleMonitorAlertConfigStatus(id: number): Promise<MonitorAlertConfigRecord> {CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts274export async function GetMonitorAlertConfigById(id: number): Promise<MonitorAlertConfigWithTriggers | undefined> {CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts281export async function GetMonitorAlertConfigsByMonitorTag(CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts297export async function GetActiveMonitorAlertConfigsWithTriggers(): Promise<MonitorAlertConfigWithTriggers[]> {CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts304export async function GetActiveMonitorAlertConfigsByMonitorTag(CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts340export async function DeleteMonitorAlertConfigsByMonitorTag(monitorTag: string): Promise<number> {CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts349export async function AddTriggerToMonitorAlertConfig(monitorAlertsId: number, triggerId: number): Promise<void> {CODE
LOW⚡…lib/server/controllers/monitorAlertConfigController.ts366export async function RemoveTriggerFromMonitorAlertConfig(monitorAlertsId: number, triggerId: number): Promise<void> {CODE
LOW⚡…lib/server/controllers/monitorAlertConfigController.ts373export async function GetMonitorAlertConfigTriggerIds(monitorAlertsId: number): Promise<number[]> {CODE
LOW⚡…lib/server/controllers/monitorAlertConfigController.ts382export async function IsTriggerUsedInMonitorAlertConfig(triggerId: number): Promise<boolean> {CODE
LOW⚡…lib/server/controllers/monitorAlertConfigController.ts389export async function GetMonitorAlertConfigsByTriggerId(triggerId: number): Promise<MonitorAlertConfigRecord[]> {CODE
LOW⚡…lib/server/controllers/monitorAlertConfigController.ts396export async function GetMonitorAlertConfigsCount(filter: MonitorAlertConfigFilter): Promise<number> {CODE
LOW⚡…lib/server/controllers/monitorAlertConfigController.ts404export async function GetMonitorAlertConfigsPaginated(CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts425export async function GetTriggersByMonitorAlertConfigId(monitorAlertsId: number): Promise<TriggerRecord[]> {CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts517export async function HasTriggeredAlertForConfig(configId: number): Promise<boolean> {CODE
LOW…lib/server/controllers/monitorAlertConfigController.ts559export async function GetAllTriggeredAlertsWithConfig(): Promise<MonitorAlertV2WithConfig[]> {CODE
LOWsrc/lib/server/controllers/monitorsController.ts490export function mergeLatestMonitoringWithSslCache(CODE
LOWsrc/lib/server/controllers/monitorsController.ts577async function removeTagFromGroupMonitors(tag: string): Promise<void> {CODE
LOW…/lib/server/controllers/userSubscriptionsController.ts67export async function GetSubscriberCountsByMethod(): Promise<{CODE
LOW…/lib/server/controllers/userSubscriptionsController.ts99export async function UpdateUserSubscriptionStatus(CODE
LOW…/lib/server/controllers/userSubscriptionsController.ts137export async function GetAdminSubscribersPaginated(CODE
LOW…/lib/server/controllers/userSubscriptionsController.ts188export async function AdminUpdateSubscriptionStatus(CODE
LOW…/lib/server/controllers/userSubscriptionsController.ts360export async function GetActiveEmailsForEventType(eventType: SubscriptionEventType): Promise<string[]> {CODE
LOW…/lib/server/controllers/userSubscriptionsController.ts551export async function UpdateSubscriberPreferences(CODE
LOWsrc/lib/server/controllers/pagesController.ts182export async function UpdatePageMonitorSettings(CODE
LOWsrc/lib/server/controllers/pagesController.ts220export async function GetPageByPathWithMonitors(CODE
LOWsrc/lib/server/controllers/layoutController.ts83function NormalizeEventDisplaySettings(settings?: Partial<EventDisplaySettings>): EventDisplaySettings {CODE
LOW⚡src/lib/server/controllers/generalTemplateController.ts7export async function GetAllGeneralEmailTemplates(): Promise<GeneralEmailTemplateRecord[]> {CODE
LOW⚡src/lib/server/controllers/generalTemplateController.ts14export async function GetGeneralEmailTemplateById(templateId: string): Promise<GeneralEmailTemplateRecord | undefined> {CODE
LOW⚡src/lib/server/controllers/generalTemplateController.ts21export async function UpdateGeneralEmailTemplate(CODE
LOWsrc/lib/components/SiteBanner.svelte32 function applyVisibilityFromStorage() {CODE
LOWsrc/lib/components/SubscribeMenu.svelte264 function ignoreCaptchaIframeInteraction(event: PointerEvent | FocusEvent) {CODE
LOWsrc/lib/components/ui/chart/chart-utils.ts18export function getPayloadConfigFromPayload(config: ChartConfig, payload: TooltipPayload, key: string) {CODE
LOW…routes/(manage)/manage/app/monitors/[tag]/+page.svelte196 async function getSiteLevelSharingConfig() {CODE
LOW…e/app/monitors/[tag]/components/MonitorTypeCard.svelte65 function isGroupLatencyCalculation(value: unknown): value is GroupLatencyCalculation {CODE
LOW…e/app/monitors/[tag]/components/MonitorTypeCard.svelte69 function createDefaultGroupTypeData(): GroupMonitorTypeData {CODE
LOW…outes/(manage)/manage/app/monitoring-data/+page.svelte89 function dateTimeStringToTimestamp(dateTimeStr: string): number {CODE
LOW…s/(manage)/manage/app/site-configurations/+page.svelte424 async function saveGlobalPageVisibilitySettings() {CODE
LOW…s/(manage)/manage/app/site-configurations/+page.svelte510 function parseEventDisplaySettings(value: unknown): EventDisplaySettings {CODE
LOW…s/(manage)/manage/app/site-configurations/+page.svelte592 async function saveMaintenanceNotificationSettings() {CODE
LOW…outes/(manage)/manage/app/pages/[page_id]/+page.svelte434 async function handleSocialPreviewUpload(event: Event): Promise<void> {CODE
LOW…anage)/manage/app/incidents/[incident_id]/+page.svelte432 async function removeMonitorFromIncident(monitorTag: string) {CODE
LOWsrc/routes/(docs)/docs/docs-utils.server.ts32function getFirstPageSlugFromSidebar(sidebar: DocsConfig["sidebar"]): string | null {CODE
LOWsrc/routes/(docs)/docs/docs-utils.server.ts255function collectVersionDocPageSlugs(version: DocsVersion): string[] {CODE
LOWsrc/routes/(docs)/docs/docs-utils.server.ts591export function parseMarkdownWithFrontMatter(slug: string): {CODE
Magic Placeholder Names8 hits · 40 pts
SeverityFileLineSnippetContext
HIGHsrc/routes/(docs)/docs/content/v4/incidents.md73 -H "Authorization: Bearer YOUR_API_KEY" \CODE
HIGHsrc/routes/(docs)/docs/content/v4/incidents.md89 -H "Authorization: Bearer YOUR_API_KEY" \CODE
HIGHsrc/routes/(docs)/docs/content/v4/monitors.md27 -H "Authorization: Bearer YOUR_API_KEY" \CODE
HIGHsrc/routes/(docs)/docs/content/v4/configuration.md102RESEND_API_KEY=your-api-keyCODE
HIGHsrc/routes/(docs)/docs/content/v4/api-reference.md19curl -H "Authorization: Bearer YOUR_API_KEY" \CODE
HIGHsrc/routes/(docs)/docs/content/v4/api-reference.md76 -H "Authorization: Bearer YOUR_API_KEY"CODE
HIGHsrc/routes/(docs)/docs/content/v4/api-reference.md83 -H "Authorization: Bearer YOUR_API_KEY" \CODE
HIGHsrc/routes/(docs)/docs/content/v3/environment-vars.md145export CLIENT_SECRET=your-api-keyCODE
Structural Annotation Overuse14 hits · 24 pts
SeverityFileLineSnippetContext
LOW.agents/skills/ss-shadcn-svelte/SKILL.md30### Step 1: Detect project setupCOMMENT
LOW.agents/skills/ss-shadcn-svelte/SKILL.md46### Step 2: Read the component documentationCOMMENT
LOW.agents/skills/ss-shadcn-svelte/SKILL.md62### Step 3: Use the right component for the jobCOMMENT
LOW…ocs)/docs/content/v4/maintenances/creating-managing.md25### Step 1: Start Creation {#step-1-start}COMMENT
LOW…ocs)/docs/content/v4/maintenances/creating-managing.md29### Step 2: Choose Schedule Type {#step-2-schedule-type}COMMENT
LOW…ocs)/docs/content/v4/maintenances/creating-managing.md45### Step 3: Basic Information {#step-3-basic-info}COMMENT
LOW…ocs)/docs/content/v4/maintenances/creating-managing.md67### Step 4: Schedule Configuration {#step-4-schedule}COMMENT
LOW…ocs)/docs/content/v4/maintenances/creating-managing.md165### Step 6: Affected Monitors {#step-6-monitors}COMMENT
LOW…ocs)/docs/content/v4/maintenances/creating-managing.md214### Step 7: Review and Create {#step-7-create}COMMENT
LOW⚡…/(docs)/docs/content/v4/getting-started/basic-setup.md24### Step 1: Create a new monitor {#create-new-monitor}COMMENT
LOW⚡…/(docs)/docs/content/v4/getting-started/basic-setup.md33### Step 2: Configure website check {#configure-website-check}COMMENT
LOW⚡…/(docs)/docs/content/v4/getting-started/basic-setup.md43### Step 3: Make it visible on status page {#make-monitor-visible}COMMENT
LOW⚡…/(docs)/docs/content/v4/getting-started/basic-setup.md50### Step 4: Verify {#verify-monitor}COMMENT
LOW…/(docs)/docs/content/v4/incidents/creating-managing.md24### Step 1: Basic Information {#basic-information}COMMENT
Over-Commented Block12 hits · 12 pts
SeverityFileLineSnippetContext
LOWdocker-compose.dev.yml1# =============================================================================COMMENT
LOWdocker-compose.yml1# =============================================================================COMMENT
LOWdocker-compose.yml41 # DATABASE_URL: sqlite://./database/kener.sqlite.dbCOMMENT
LOWdocker-compose.yml61 volumes:COMMENT
LOWdocker-compose.yml81 # healthcheck:COMMENT
LOWdocker-compose.yml101 # healthcheck:COMMENT
LOWknexfile.ts21const keepAliveEnabled = process.env.DATABASE_KEEPALIVE !== "false";COMMENT
LOW.github/dependabot.yml21 prefix: "os"COMMENT
LOWsrc/hooks.ts1import type { Reroute } from "@sveltejs/kit";COMMENT
LOWsrc/lib/server/db/poolContext.ts1import { AsyncLocalStorage } from "node:async_hooks";COMMENT
LOWsrc/lib/components/Captcha.svelte1<script module lang="ts">COMMENT
LOWsrc/lib/components/Captcha.svelte161 sitekey: siteKey,COMMENT
Example Usage Blocks3 hits · 7 pts
SeverityFileLineSnippetContext
LOW⚡docker-compose.dev.yml6# Usage:COMMENT
LOW⚡docker-compose.status.yml4# Usage:COMMENT
LOW⚡docker-compose.yml4# Usage:COMMENT
Fake / Example Data5 hits · 5 pts
SeverityFileLineSnippetContext
LOWsrc/lib/server/tool.test.ts336 expect(ValidateEmail("user@example.com")).toBe(true);CODE
LOWsrc/lib/server/controllers/commonController.test.ts12 const forged = jwt.sign({ id: 1, email: "admin@example.com" }, "DUMMY_SECRET");CODE
LOWsrc/routes/(manage)/manage/app/users/+page.svelte527 <Input id="name" type="text" placeholder="John Doe" bind:value={newUser.name} required />CODE
LOWsrc/routes/(api)/api/v4/write-parity.test.ts67const ADMIN_EMAIL = "admin@example.com";CODE
LOWsrc/routes/(docs)/docs/content/v3/customize-site.md239 description: "loroem ipsum lorem ipsum"CODE
AI Slop Vocabulary1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMpackage-lock.json9285 "resolved": "https://registry.npmjs.org/robust-predicates/-/robust-predicates-3.0.2.tgz",CODE