AI Slop Code Risk Monitor

Infisical/agent-vault

SlopCodeMonitor badge for Infisical/agent-vault Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A HTTP credential proxy and vault for AI agents like Claude Code, OpenClaw, Hermes, custom agents + harnesses, and more.

0.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for Infisical/agent-vault, a Go project with 2,458 GitHub stars. SynthScan examined 94,298 lines of code across 378 source files, recording 52 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 0.9 (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.9
Adjusted Signal
0.9
Raw Pattern Score
100%
Time Factor
2026-10-27
Last Push
2.5K
Stars
Go
Language
94.3K
Lines of Code
378
Files
52
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.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

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

Agent Over-Engineering Ratio 1.6/100 · LOW

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

PR Review Velocity Impact 4.0/100 · LOW

Which changes need focused human review? 52 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 12LOW 40

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 52 distinct pattern matches across 7 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 Separators10 hits · 30 pts
SeverityFileLineSnippetContext
MEDIUMinstall.sh24# ── Helpers ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMinstall.sh53# ── Detect platform ─────────────────────────────────────────────────────────COMMENT
MEDIUMinstall.sh71# ── Main ─────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinstall.sh83 # ── Check for existing installation ──────────────────────────────────COMMENT
MEDIUMinstall.sh92 # ── Stop running server ──────────────────────────────────────────COMMENT
MEDIUMinstall.sh113 # ── Back up database ─────────────────────────────────────────────COMMENT
MEDIUMinstall.sh125 # ── Fetch latest version ─────────────────────────────────────────────COMMENT
MEDIUMinstall.sh138 # ── Download and extract ─────────────────────────────────────────────COMMENT
MEDIUMinstall.sh160 # ── Install ──────────────────────────────────────────────────────────COMMENT
MEDIUMinstall.sh164 # ── Verify ───────────────────────────────────────────────────────────COMMENT
Over-Commented Block25 hits · 25 pts
SeverityFileLineSnippetContext
LOWinstall.sh1#!/bin/shCOMMENT
LOWcmd/run.go541// and HTTPS through the broker. Returns (env, 0, false, nil) when theCOMMENT
LOWcmd/helpers.go521const (COMMENT
LOWinternal/brokercore/proxyauth.go1package brokercoreCOMMENT
LOWinternal/broker/broker.go701// existing service adopts that service's Name.COMMENT
LOWinternal/ca/soft.go61 // Store, when non-nil, causes the CA to load/save its root from aCOMMENT
LOWinternal/mitm/isolation_loopback_test.go1package mitmCOMMENT
LOWinternal/mitm/proxy.go1// Package mitm implements an HTTP/1.1 forward-proxy ingress for agentCOMMENT
LOWinternal/mitm/proxy.go121 return pCOMMENT
LOWinternal/mitm/proxy.go181 // Origin-form (no scheme/host), https://, ws://, file://, gopher://,COMMENT
LOWinternal/mitm/forward.go41 }COMMENT
LOWinternal/mitm/forward.go81// and the scope is resolved per request rather than onceCOMMENT
LOWinternal/server/server.go101// MITM ingress can share the same tier state (see cmd/server.go).COMMENT
LOWinternal/server/server.go981COMMENT
LOWinternal/server/handle_mitm.go1package serverCOMMENT
LOWinternal/server/handle_skills.go21//COMMENT
LOWinternal/ratelimit/ratelimit.go21 // forward-proxy requests where authentication fails). SlidingCOMMENT
LOWinternal/proposal/proposal.go21// Action represents the operation a proposed service or credential slot performs.COMMENT
LOWinternal/isolation/env.go21// (host-local vs container-local bind mount).COMMENT
LOWinternal/isolation/gateway.go1package isolationCOMMENT
LOWinternal/requestlog/sink.go1// Package requestlog persists per-request broker metadata (method, host,COMMENT
LOWinternal/netguard/netguard.go161 }COMMENT
LOWinternal/store/store.go621 // ReplaceVaultCredentialsForSync rewrites credentials only while theCOMMENT
LOWinternal/store/sql_store.go161 return s.dialect.Name()COMMENT
LOWexamples/nginx-public-ui-proxy/docker-compose.yml21 - agent-vaultCOMMENT
Verbosity Indicators5 hits · 10 pts
SeverityFileLineSnippetContext
LOW⚡cmd/service_interactive.go39 // Step 1: Vault selectionCOMMENT
LOW⚡cmd/service_interactive.go45 // Step 2: Check existing servicesCOMMENT
LOWcmd/service_interactive.go56 // Step 3: Service builder loopCOMMENT
LOW⚡cmd/service_interactive.go79 // Step 5: PreviewCOMMENT
LOW⚡cmd/service_interactive.go83 // Step 6: ConfirmCOMMENT
Structural Annotation Overuse5 hits · 10 pts
SeverityFileLineSnippetContext
LOW⚡cmd/service_interactive.go39 // Step 1: Vault selectionCOMMENT
LOW⚡cmd/service_interactive.go45 // Step 2: Check existing servicesCOMMENT
LOWcmd/service_interactive.go56 // Step 3: Service builder loopCOMMENT
LOW⚡cmd/service_interactive.go79 // Step 5: PreviewCOMMENT
LOW⚡cmd/service_interactive.go83 // Step 6: ConfirmCOMMENT
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMinternal/isolation/gateway.go20// a different bridge). To be robust across versions we bind 0.0.0.0.COMMENT
MEDIUMexamples/nginx-public-ui-proxy/docker-compose.yml23 # Verification harness for trust-header stripping: uncomment, then in theCOMMENT
Fake / Example Data4 hits · 4 pts
SeverityFileLineSnippetContext
LOWcmd/reauth_test.go272 return &session.ClientSession{Token: "fresh", Address: s.Address, Email: "user@example.com"}, nilCODE
LOWcmd/reauth_test.go298 if sess.Token != "fresh" || sess.Email != "user@example.com" {CODE
LOWcmd/skill_cli.md92 {"key": "TELEGRAM_BOT_TOKEN", "placeholder": "__bot_token__", "in": ["path"]}CODE
LOWinternal/broker/broker.go67 Placeholder string `yaml:"placeholder" json:"placeholder"`CODE
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWweb/src/router.tsx73async function requireInitializedOrRedirect() {CODE