Home / nanbingxyz / 5ire
AI Slop Code Risk Monitor

nanbingxyz/5ire

SlopCodeMonitor badge for nanbingxyz/5ire Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

5ire is a cross-platform desktop AI assistant, MCP client. It compatible with major service providers, supports local knowledge base and tools via model context protocol servers .

0.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for nanbingxyz/5ire, a TypeScript project with 5,373 GitHub stars. SynthScan examined 74,989 lines of code across 361 source files, recording 15 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.2 (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.2
Adjusted Signal
0.2
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
5.4K
Stars
TypeScript
Language
75.0K
Lines of Code
361
Files
15
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 1.1/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.5/100 · LOW

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

PR Review Velocity Impact 1.1/100 · LOW

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

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

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 14

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 15 distinct pattern matches across 4 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.

Hyper-Verbose Identifiers8 hits · 8 pts
SeverityFileLineSnippetContext
LOW…/renderer/components/MCPServerApprovalPolicyDialog.tsx33const MCPServerApprovalPolicyDialog = function MCPServerApprovalPolicyDialog(CODE
LOWsrc/utils/util.ts419export function extractFirstLevelBrackets(text: string): string[] {CODE
LOWsrc/utils/util.ts552export function removeAdditionalProperties(schema: any): any {CODE
LOWsrc/utils/util.ts583export function addStringTypeToEnumProperty(schema: any): any {CODE
LOWsrc/main/mcp.ts50function validateAndGetProxy(proxyUrl: string): string {CODE
LOWsrc/main/sqlite.ts151 function createTableKnowledgeCollections() {CODE
LOWsrc/main/sqlite.ts167 function createTableKnowledgeFiles() {CODE
LOWsrc/main/sqlite.ts187 function createTableChatKnowledgeRels() {CODE
Over-Commented Block5 hits · 5 pts
SeverityFileLineSnippetContext
LOWscripts/daily-summary.ts1// scripts/daily-summary.tsCOMMENT
LOWsrc/renderer/components/Assets.tsx1// import DarkDesign from 'assets/images/design.dark.png'; //704COMMENT
LOWsrc/intellichat/types/index.ts61 | {COMMENT
LOWsrc/main/next/document-loader/EpubLoader.ts1// TODO: Add epub supportCOMMENT
LOWsrc/main/next/document-loader/EpubLoader.ts21// };COMMENT
Modern AI Meta-Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMdocs/ARCHITECTURE.md163### Knowledge Base (RAG)COMMENT
Slop Phrases1 hit · 1 pts
SeverityFileLineSnippetContext
LOWpublic/locales/en/translation.json341 "Common.Placeholder.APIKey": "Most providers require an API key – don't forget to set yours here",CODE