Repository Analysis

NoFxAiOS/nofx

Your AI trading terminal assistant for US stocks, commodities, forex, and crypto.

6.6 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of NoFxAiOS/nofx, a Go project with 12,556 GitHub stars. SynthScan v2.0 examined 168,118 lines of code across 567 source files, recording 408 pattern matches distributed across 16 syntactic categories. The overall adjusted score of 6.6 places this repository in the Low AI signal band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

6.6
Adjusted Score
6.6
Raw Score
100%
Time Factor
2026-07-11
Last Push
12.6K
Stars
Go
Language
168.1K
Lines of Code
567
Files
408
Pattern Hits
2026-07-14
Scan Date
0.03
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 19MEDIUM 219LOW 170

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 408 distinct pattern matches across 16 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

AI Slop Vocabulary118 hits · 386 pts
SeverityFileLineSnippetContext
MEDIUMweb/src/types/strategy.ts198 // Trading Leverage - exchange leverage for opening positions (AI guided)COMMENT
MEDIUMweb/src/types/strategy.ts199 btc_eth_max_leverage: number; // BTC/ETH max exchange leverageCODE
MEDIUMweb/src/types/strategy.ts200 altcoin_max_leverage: number; // Altcoin max exchange leverageCODE
MEDIUMweb/src/components/landing/brand/Marquee.tsx16 // Clone children to create seamless loopCOMMENT
MEDIUMtrader/grid_regime.go36// getRegimeLeverageLimit returns the effective leverage limit for a regime levelCOMMENT
MEDIUMtrader/auto_trader_grid_regime.go239 // Calculate effective leverageCOMMENT
MEDIUMtrader/auto_trader_grid_regime.go284 // Use default leverage limits since GridStrategyConfig doesn't have regime-specific limitsCOMMENT
MEDIUMtrader/auto_trader_grid.go338 // CRITICAL: Set leverage on exchange before tradingCOMMENT
MEDIUMtrader/auto_trader_grid.go341 // Not fatal - continue with default leverageCOMMENT
MEDIUMtrader/interface.go34 // CRITICAL FIX: Set leverage before placing orderCOMMENT
MEDIUMtrader/interface.go38 // Continue anyway - some exchanges don't require explicit leverage settingCOMMENT
MEDIUMtrader/auto_trader_grid_orders.go69 // This protects against AI miscalculations or leverage misconfigurationsCOMMENT
MEDIUMtrader/auto_trader.go428 // ClampLimits above bounds it (ratio 0.5–10, leverage caps), and theCOMMENT
MEDIUMtrader/auto_trader.go690// calculatePnLPercentage calculates P&L percentage (based on margin, automatically considers leverage)COMMENT
MEDIUMtrader/auto_trader_loop.go510 // Calculate P&L percentage (based on margin, considering leverage)COMMENT
MEDIUMtrader/auto_trader_loop.go595 // 5. Get leverage from strategy configCOMMENT
MEDIUMtrader/auto_trader_orders.go15 // totalRequired ≈ positionSize/leverage + positionSize*takerFeeRate + positionSize/leverage*1%COMMENT
MEDIUMtrader/auto_trader_orders.go16 // = positionSize * (marginOverheadFactor/leverage + takerFeeRate)COMMENT
MEDIUMtrader/okx/trader_orders.go19 // Set leverageCOMMENT
MEDIUMtrader/okx/trader_orders.go100 // Set leverageCOMMENT
MEDIUMtrader/okx/trader_orders.go819 // Set leverage if specifiedCOMMENT
MEDIUMtrader/okx/trader_account.go91// to all subsequent leverage and order requests for this trader instance.COMMENT
MEDIUMtrader/okx/trader_account.go97// /api/v5/account/set-leverage and via the tdMode field on order placement.COMMENT
MEDIUMtrader/okx/trader_account.go108 // while leverage uses mgnMode on /account/set-leverage.COMMENT
MEDIUMtrader/okx/trader_account.go109 // Persist the configured mode locally so subsequent leverage/order calls use it,COMMENT
MEDIUMtrader/okx/trader_account.go115// SetLeverage sets leverageCOMMENT
MEDIUMtrader/okx/trader_account.go120 // Set leverage for both long and shortCOMMENT
MEDIUMtrader/okx/trader_account.go131 // Ignore if already at target leverageCOMMENT
MEDIUMtrader/okx/trader.go44 // Margin mode setting used for new orders and leverage changes.COMMENT
MEDIUMtrader/hyperliquid/trader_orders.go61 // Set leverage before order placement. Hyperliquid supports leverageCOMMENT
MEDIUMtrader/hyperliquid/trader_orders.go63 // at whatever leverage they had previously selected (for example 20x).COMMENT
MEDIUMtrader/hyperliquid/trader_orders.go134 // Set leverage before order placement. Hyperliquid supports leverageCOMMENT
MEDIUMtrader/hyperliquid/trader_orders.go136 // at whatever leverage they had previously selected (for example 20x).COMMENT
MEDIUMtrader/hyperliquid/trader_orders.go1034 // Set leverage if specified.COMMENT
MEDIUMtrader/hyperliquid/trader_positions.go121 // Get leverage (default to 1 if not available)COMMENT
MEDIUMtrader/hyperliquid/trader_positions.go153// SetLeverage sets leverageCOMMENT
MEDIUMtrader/hyperliquid/trader_positions.go158 // Call UpdateLeverage (leverage int, name string, isCross bool)COMMENT
MEDIUMtrader/types/interface.go62 // SetLeverage Set leverageCOMMENT
MEDIUMtrader/types/interface.go176 // CRITICAL FIX: Set leverage before placing orderCOMMENT
MEDIUMtrader/types/interface.go180 // Continue anyway - some exchanges don't require explicit leverage settingCOMMENT
MEDIUMtrader/indodax/trader_orders.go123// SetLeverage is a no-op for Indodax (spot-only, no leverage)COMMENT
MEDIUMtrader/indodax/trader.go28// Since Indodax is spot-only, futures-specific methods (OpenShort, CloseShort, leverage, etc.)COMMENT
MEDIUMtrader/aster/trader_orders.go27 // Set leverage first (non-fatal if position already exists)COMMENT
MEDIUMtrader/aster/trader_orders.go29 // Error -2030: Cannot adjust leverage when position existsCOMMENT
MEDIUMtrader/aster/trader_orders.go30 // This is expected when adding to an existing position, continue with current leverageCOMMENT
MEDIUMtrader/aster/trader_orders.go100 // Set leverage first (non-fatal if position already exists)COMMENT
MEDIUMtrader/aster/trader_orders.go102 // Error -2030: Cannot adjust leverage when position existsCOMMENT
MEDIUMtrader/aster/trader_orders.go103 // This is expected when adding to an existing position, continue with current leverageCOMMENT
MEDIUMtrader/aster/trader_test.go168 // Mock SetLeverage - /fapi/v1/leverageCOMMENT
MEDIUMtrader/aster/trader_positions.go112// SetLeverage Set leverage multiplierCOMMENT
MEDIUMtrader/bybit/trader_orders.go28 // Set leverage firstCOMMENT
MEDIUMtrader/bybit/trader_orders.go71 // Set leverage firstCOMMENT
MEDIUMtrader/bybit/trader_orders.go191// SetLeverage sets leverageCOMMENT
MEDIUMtrader/bybit/trader_orders.go202 // If leverage is already at target value, Bybit will return an error, ignore this caseCOMMENT
MEDIUMtrader/bybit/trader_orders.go209 if result.RetCode != 0 && result.RetCode != 110043 { // 110043 = leverage not modifiedCODE
MEDIUMtrader/bybit/trader_orders.go599 // Set leverage if specifiedCOMMENT
MEDIUMtrader/kucoin/trader_orders.go21 // Set leverageCOMMENT
MEDIUMtrader/kucoin/trader_orders.go78 // Set leverageCOMMENT
MEDIUMtrader/kucoin/trader_orders.go525// SetLeverage sets leverage for a symbolCOMMENT
MEDIUMtrader/kucoin/trader_orders.go536 // Ignore if already at target leverageCOMMENT
58 more matches not shown…
Decorative Section Separators93 hits · 300 pts
SeverityFileLineSnippetContext
MEDIUMstart.sh3# ═══════════════════════════════════════════════════════════════COMMENT
MEDIUMstart.sh6# ═══════════════════════════════════════════════════════════════COMMENT
MEDIUMstart.sh10# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh12# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh20# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh22# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh67# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh69# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh79# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh81# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh245# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh247# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh254# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh256# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh263# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh265# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh274# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh276# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh302# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh304# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh312# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh314# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh39# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh41# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh54# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh56# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh104# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh106# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh126# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh128# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh173# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh175# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh192# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh194# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh205# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh207# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh287# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh289# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh348# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh350# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh376# ------------------------------------------------------------------------COMMENT
MEDIUMstart.sh378# ------------------------------------------------------------------------COMMENT
MEDIUMweb/src/components/terminal/RiskRadar.tsx133 // ── one-glance verdicts ──────────────────────────────────────────────COMMENT
MEDIUMweb/src/components/terminal/RiskRadar.tsx297// ── verdict tag ────────────────────────────────────────────────────────COMMENT
MEDIUMweb/src/components/terminal/RiskRadar.tsx340// ── bilingual label block ──────────────────────────────────────────────COMMENT
MEDIUMweb/src/data/faqData.ts51 // ───────────────────────── Getting started ─────────────────────────COMMENT
MEDIUMweb/src/data/faqData.ts141 // ───────────────────────── Launch & wallets ─────────────────────────COMMENT
MEDIUMweb/src/data/faqData.ts253 // ───────────────────────── Trading & execution ─────────────────────────COMMENT
MEDIUMweb/src/data/faqData.ts409 // ───────────────────────── Dashboard & metrics ─────────────────────────COMMENT
MEDIUMweb/src/data/faqData.ts464 // ───────────────────────── Security ─────────────────────────COMMENT
MEDIUMweb/src/data/faqData.ts511 // ───────────────────────── Self-hosting ─────────────────────────COMMENT
MEDIUMweb/src/data/faqData.ts601 // ───────────────────────── Contributing ─────────────────────────COMMENT
MEDIUMmcp/hooks.go14 // ── Simple CallWithMessages path ────────────────────────────────────────COMMENT
MEDIUMmcp/hooks.go18 // ── Shared request plumbing ─────────────────────────────────────────────COMMENT
MEDIUMmcp/hooks.go24 // ── Advanced (Request-object) path ──────────────────────────────────────COMMENT
MEDIUMmcp/payment/claw402.go226// ── Format overrides for Anthropic endpoints ─────────────────────────────────COMMENT
MEDIUMmcp/payment/x402.go127// ── Shared x402 types ────────────────────────────────────────────────────────COMMENT
MEDIUMmcp/payment/x402.go158// ── Shared x402 helpers ──────────────────────────────────────────────────────COMMENT
MEDIUMmcp/payment/x402.go628// ── Shared EIP-712 constants & helpers (Base chain, USDC) ────────────────────COMMENT
MEDIUMmcp/provider/claude.go5// ┌─────────────────────┬───────────────────────────┬─────────────────────────────────┐COMMENT
33 more matches not shown…
Structural Annotation Overuse74 hits · 140 pts
SeverityFileLineSnippetContext
LOWtrader/position_snapshot.go21 // Step 1: Delete all OPEN positionsCOMMENT
LOWtrader/position_snapshot.go28 // Step 2: Get current positions from exchangeCOMMENT
LOWtrader/position_snapshot.go42 // Step 3: Create snapshot record for each positionCOMMENT
LOWtrader/hyperliquid/trader_account.go20 // Step 1: Query Spot account balanceCOMMENT
LOWtrader/hyperliquid/trader_account.go35 // Step 2: Query Perpetuals contract account statusCOMMENT
LOWtrader/hyperliquid/trader_account.go45 // Step 3: Dynamically select correct summary based on margin mode (CrossMarginSummary or MarginSummary)COMMENT
LOWtrader/hyperliquid/trader_account.go93 // Step 4: Use Withdrawable field (PR #443)COMMENT
LOWtrader/hyperliquid/trader_account.go113 // Step 5: Query xyz dex balance (stock perps, forex, commodities)COMMENT
LOWtrader/hyperliquid/trader_account.go149 // Step 7: Unified Account mode - Spot USDC is used as collateral for PerpsCOMMENT
LOWtrader/lighter/integration_test.go861 // Step 2: Set leverageCOMMENT
LOWtrader/lighter/integration_test.go871 // Step 3: Open Long PositionCOMMENT
LOWtrader/lighter/integration_test.go881 // Step 4: Verify positionCOMMENT
LOWtrader/lighter/integration_test.go891 // Step 5: Place limit order (sell at higher price)COMMENT
LOWtrader/lighter/integration_test.go914 // Step 7: Cancel all ordersCOMMENT
LOWtrader/lighter/integration_test.go924 // Step 8: Close positionCOMMENT
LOWtrader/lighter/integration_test.go934 // Step 9: Verify position closedCOMMENT
LOWtrader/lighter/integration_test.go943 // Step 10: Get final balanceCOMMENT
LOWtrader/lighter/integration_test.go848 // Step 1: Get initial stateCOMMENT
LOWtrader/lighter/integration_test.go902 // Step 6: Get open ordersCOMMENT
LOWtrader/binance/order_sync.go64 // Step 1: Get max trade IDs from local DB for incremental syncCOMMENT
LOWtrader/binance/order_sync.go71 // Step 2: Detect symbols to sync using multiple methodsCOMMENT
LOWtrader/binance/order_sync.go130 // Step 3: Query trades for changed symbols using fromId (incremental) or time-based (new symbols)COMMENT
LOWtrader/binance/order_sync_test.go256 // Step 1: Determine lastSyncTime (simulating first run)COMMENT
LOWtrader/binance/order_sync_test.go260 // Step 2: Detect symbols using all methodsCOMMENT
LOWtrader/binance/order_sync_test.go329 // Step 3: Query trades for each symbolCOMMENT
LOWtrader/binance/sync_verify_test.go41 // Step 1: Run syncCOMMENT
LOWtrader/binance/sync_verify_test.go51 // Step 2: Get all trades from exchange for verificationCOMMENT
LOWtrader/binance/sync_verify_test.go102 // Step 3: Get all fills from DBCOMMENT
LOWtrader/binance/sync_verify_test.go123 // Step 4: Check for missing tradesCOMMENT
LOWtrader/binance/sync_verify_test.go150 // Step 5: Check for extra/duplicate tradesCOMMENT
LOWtrader/binance/sync_verify_test.go177 // Step 6: Check for data accuracyCOMMENT
LOWtrader/binance/sync_verify_test.go243 // Step 7: Summary by symbolCOMMENT
LOWtrader/binance/sync_verify_test.go304 // Step 8: Position verificationCOMMENT
LOWmcp/client.go383 // Step 1: Build request body (via hooks for dynamic dispatch)COMMENT
LOWmcp/client.go386 // Step 2: Serialize request body (via hooks for dynamic dispatch)COMMENT
LOWmcp/client.go392 // Step 3: Build URL (via hooks for dynamic dispatch)COMMENT
LOWmcp/client.go396 // Step 4: Create HTTP request (fixed logic)COMMENT
LOWmcp/client.go402 // Step 5: Send HTTP request (fixed logic)COMMENT
LOWmcp/client.go409 // Step 6: Read response body (fixed logic)COMMENT
LOWmcp/client.go415 // Step 7: Check HTTP status code (fixed logic)COMMENT
LOWmcp/client.go420 // Step 8: Parse response (via hooks for dynamic dispatch)COMMENT
LOWdocs/research/AI-Trader-Analysis-Report.md536 # Step 1: 连接MCP服务COMMENT
LOWdocs/research/AI-Trader-Analysis-Report.md540 # Step 2: 加载工具COMMENT
LOWdocs/research/AI-Trader-Analysis-Report.md544 # Step 3: 初始化LLM (根据模型类型选择适配器)COMMENT
LOWdocs/research/AI-Trader-Analysis-Report.md547 # Step 4: 绑定工具COMMENT
LOWdocs/maintainers/SETUP_GUIDE.md36### Step 1: Sync GitHub LabelsCOMMENT
LOWdocs/maintainers/SETUP_GUIDE.md72### Step 2: Enable GitHub ActionsCOMMENT
LOWdocs/maintainers/SETUP_GUIDE.md79### Step 3: Set Up Branch Protection RulesCOMMENT
LOWdocs/maintainers/SETUP_GUIDE.md103### Step 4: Create GitHub ProjectsCOMMENT
LOWdocs/maintainers/SETUP_GUIDE.md115### Step 5: Enable Discussions (Optional but Recommended)COMMENT
LOWdocs/maintainers/SETUP_GUIDE.md126### Step 6: Configure Issue TemplatesCOMMENT
LOWdocs/maintainers/SETUP_GUIDE.md138### Step 7: Set Up Code Owners (Optional)COMMENT
LOWdocs/maintainers/SETUP_GUIDE.md160### Step 8: Configure NotificationsCOMMENT
LOWdocs/getting-started/lighter-agent-wallet.md17## Step 1: Connect Your Main WalletCOMMENT
LOWdocs/getting-started/lighter-agent-wallet.md24## Step 2: Create Agent WalletCOMMENT
LOWdocs/getting-started/lighter-agent-wallet.md31## Step 3: Save Agent CredentialsCOMMENT
LOWdocs/getting-started/lighter-agent-wallet.md43## Step 4: Configure in NOFXCOMMENT
LOWdocs/getting-started/hyperliquid-agent-wallet.md17## Step 1: Connect Your Main WalletCOMMENT
LOWdocs/getting-started/hyperliquid-agent-wallet.md24## Step 2: Create Agent WalletCOMMENT
LOWdocs/getting-started/hyperliquid-agent-wallet.md32## Step 3: Save Agent CredentialsCOMMENT
14 more matches not shown…
Magic Placeholder Names16 hits · 108 pts
SeverityFileLineSnippetContext
HIGHdocs/getting-started/custom-api.md103 "custom_api_key": "your-api-key",CODE
HIGHdocs/getting-started/custom-api.en.md103 "custom_api_key": "your-api-key",CODE
HIGHdocs/api/API_REFERENCE.md16GET /api/ai500/list?auth=your_api_keyCODE
HIGHdocs/api/API_REFERENCE.md22Authorization: Bearer your_api_keyCODE
HIGHdocs/api/API_REFERENCE.md665curl "https://nofxos.ai/api/ai500/list?auth=your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md669 -H "Authorization: Bearer your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md672curl "https://nofxos.ai/api/price/ranking?duration=1h&limit=20&auth=your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md675curl "https://nofxos.ai/api/price/ranking?duration=1h,4h,24h&limit=10&auth=your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md678curl "https://nofxos.ai/api/coin/BTC?auth=your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md681curl "https://nofxos.ai/api/coin/BTC?include=netflow,oi&auth=your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md684curl "https://nofxos.ai/api/oi/top-ranking?duration=4h&limit=50&auth=your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md687curl "https://nofxos.ai/api/oi/low-ranking?duration=24h&limit=30&auth=your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md690curl "https://nofxos.ai/api/netflow/top-ranking?type=institution&trade=future&duration=1h&auth=your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md693curl "https://nofxos.ai/api/netflow/low-ranking?type=personal&trade=spot&duration=4h&auth=your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md702API_KEY = "your_api_key"CODE
HIGHdocs/api/API_REFERENCE.md783const API_KEY = "your_api_key";CODE
Verbosity Indicators41 hits · 80 pts
SeverityFileLineSnippetContext
LOWtrader/position_snapshot.go21 // Step 1: Delete all OPEN positionsCOMMENT
LOWtrader/position_snapshot.go28 // Step 2: Get current positions from exchangeCOMMENT
LOWtrader/position_snapshot.go42 // Step 3: Create snapshot record for each positionCOMMENT
LOWtrader/hyperliquid/trader_account.go20 // Step 1: Query Spot account balanceCOMMENT
LOWtrader/hyperliquid/trader_account.go35 // Step 2: Query Perpetuals contract account statusCOMMENT
LOWtrader/hyperliquid/trader_account.go45 // Step 3: Dynamically select correct summary based on margin mode (CrossMarginSummary or MarginSummary)COMMENT
LOWtrader/hyperliquid/trader_account.go93 // Step 4: Use Withdrawable field (PR #443)COMMENT
LOWtrader/hyperliquid/trader_account.go113 // Step 5: Query xyz dex balance (stock perps, forex, commodities)COMMENT
LOWtrader/hyperliquid/trader_account.go149 // Step 7: Unified Account mode - Spot USDC is used as collateral for PerpsCOMMENT
LOWtrader/lighter/integration_test.go861 // Step 2: Set leverageCOMMENT
LOWtrader/lighter/integration_test.go871 // Step 3: Open Long PositionCOMMENT
LOWtrader/lighter/integration_test.go881 // Step 4: Verify positionCOMMENT
LOWtrader/lighter/integration_test.go891 // Step 5: Place limit order (sell at higher price)COMMENT
LOWtrader/lighter/integration_test.go914 // Step 7: Cancel all ordersCOMMENT
LOWtrader/lighter/integration_test.go924 // Step 8: Close positionCOMMENT
LOWtrader/lighter/integration_test.go934 // Step 9: Verify position closedCOMMENT
LOWtrader/lighter/integration_test.go943 // Step 10: Get final balanceCOMMENT
LOWtrader/lighter/integration_test.go848 // Step 1: Get initial stateCOMMENT
LOWtrader/lighter/integration_test.go902 // Step 6: Get open ordersCOMMENT
LOWtrader/binance/order_sync.go64 // Step 1: Get max trade IDs from local DB for incremental syncCOMMENT
LOWtrader/binance/order_sync.go71 // Step 2: Detect symbols to sync using multiple methodsCOMMENT
LOWtrader/binance/order_sync.go130 // Step 3: Query trades for changed symbols using fromId (incremental) or time-based (new symbols)COMMENT
LOWtrader/binance/order_sync_test.go256 // Step 1: Determine lastSyncTime (simulating first run)COMMENT
LOWtrader/binance/order_sync_test.go260 // Step 2: Detect symbols using all methodsCOMMENT
LOWtrader/binance/order_sync_test.go329 // Step 3: Query trades for each symbolCOMMENT
LOWtrader/binance/sync_verify_test.go41 // Step 1: Run syncCOMMENT
LOWtrader/binance/sync_verify_test.go51 // Step 2: Get all trades from exchange for verificationCOMMENT
LOWtrader/binance/sync_verify_test.go102 // Step 3: Get all fills from DBCOMMENT
LOWtrader/binance/sync_verify_test.go123 // Step 4: Check for missing tradesCOMMENT
LOWtrader/binance/sync_verify_test.go150 // Step 5: Check for extra/duplicate tradesCOMMENT
LOWtrader/binance/sync_verify_test.go177 // Step 6: Check for data accuracyCOMMENT
LOWtrader/binance/sync_verify_test.go243 // Step 7: Summary by symbolCOMMENT
LOWtrader/binance/sync_verify_test.go304 // Step 8: Position verificationCOMMENT
LOWmcp/client.go383 // Step 1: Build request body (via hooks for dynamic dispatch)COMMENT
LOWmcp/client.go386 // Step 2: Serialize request body (via hooks for dynamic dispatch)COMMENT
LOWmcp/client.go392 // Step 3: Build URL (via hooks for dynamic dispatch)COMMENT
LOWmcp/client.go396 // Step 4: Create HTTP request (fixed logic)COMMENT
LOWmcp/client.go402 // Step 5: Send HTTP request (fixed logic)COMMENT
LOWmcp/client.go409 // Step 6: Read response body (fixed logic)COMMENT
LOWmcp/client.go415 // Step 7: Check HTTP status code (fixed logic)COMMENT
LOWmcp/client.go420 // Step 8: Parse response (via hooks for dynamic dispatch)COMMENT
Example Usage Blocks14 hits · 21 pts
SeverityFileLineSnippetContext
LOWinstall.sh6# Usage:COMMENT
LOWinstall-stable.sh5# Usage:COMMENT
LOWmcp/options.go17// Usage example:COMMENT
LOWmcp/options.go31// Usage example:COMMENT
LOWmcp/options.go46// Usage example:COMMENT
LOWmcp/options.go57// Usage example:COMMENT
LOWmcp/options.go67// Usage example:COMMENT
LOWmcp/options.go81// Usage example:COMMENT
LOWmcp/options.go93// Usage example:COMMENT
LOWmcp/options.go104// Usage example:COMMENT
LOWmcp/options.go157// Usage example:COMMENT
LOWmcp/options.go170// Usage example:COMMENT
LOWmcp/options.go183// Usage example:COMMENT
LOWmcp/request_builder.go24// Usage example:COMMENT
Over-Commented Block19 hits · 19 pts
SeverityFileLineSnippetContext
LOWinstall.sh1#!/bin/bashCOMMENT
LOWcli.go21)COMMENT
LOWweb/src/pages/StrategyMarketPage.tsx21 title={t('strategyMarket', language) || 'Strategy Market'}COMMENT
LOWtrader/auto_trader_loop.go201 if at.isSafeMode() {COMMENT
LOWtrader/auto_trader_loop.go221 // logger.Infof("📋 AI decision list (%d items):\n", len(kernel.Decisions))COMMENT
LOWtrader/okx/trader_account.go81 // Update cacheCOMMENT
LOWtrader/lighter/trader.go581 // 2. side: BUY or SELLCOMMENT
LOWprovider/hyperliquid/kline.go461}COMMENT
LOWmcp/interface.go21 // Returns the complete final text when done.COMMENT
LOWmcp/request_builder.go21COMMENT
LOWmcp/client.go81 // Hooks are used to implement dynamic dispatch (polymorphism)COMMENT
LOWmcp/client.go101// // Custom loggerCOMMENT
LOWmcp/intro/BUILDER_EXAMPLES.md461 response, err := client.CallWithRequest(request)COMMENT
LOWmcp/provider/claude.go1// Package provider — ClaudeClient implements the Anthropic Messages API.COMMENT
LOWtelegram/agent/agent.go181 return sb.String()COMMENT
LOWtelegram/agent/apicall.go41// botAPIAllowlist enumerates the endpoints the Telegram LLM agent is permittedCOMMENT
LOWapi/server.go181 s.route(api, "POST", "/strategies/estimate-tokens", "Estimate token usage for a strategy config", s.handleEstimateTokeCOMMENT
LOWkernel/engine_prompt.go141 }COMMENT
LOWstore/position_reconcile.go21//COMMENT
Excessive Try-Catch Wrapping10 hits · 17 pts
SeverityFileLineSnippetContext
LOWdocs/research/AI-Trader-Analysis-Report.md727 except Exception as e:CODE
LOWdocs/research/AI-Trader-Analysis-Report.md1374 except Exception as e:CODE
MEDIUM.github/workflows/scripts/calculate_coverage.py26 print(f"Error: Coverage file {coverage_file} not found", file=sys.stderr)CODE
MEDIUM.github/workflows/scripts/calculate_coverage.py40 print(f"Error running go tool cover: {e}", file=sys.stderr)CODE
MEDIUM.github/workflows/scripts/calculate_coverage.py128 print(f"Error generating coverage report: {e}", file=sys.stderr)CODE
MEDIUM.github/workflows/scripts/comment_pr.py101 print(f"Error fetching comments: {e}", file=sys.stderr)STRING
MEDIUM.github/workflows/scripts/comment_pr.py132 print(f"Error posting comment: {e}", file=sys.stderr)STRING
MEDIUM.github/workflows/scripts/comment_pr.py164 print(f"Error updating comment: {e}", file=sys.stderr)STRING
MEDIUM.github/workflows/scripts/comment_pr.py216 print("Error: GITHUB_TOKEN environment variable not set", file=sys.stderr)CODE
MEDIUM.github/workflows/scripts/comment_pr.py220 print("Error: GITHUB_REPOSITORY environment variable not set", file=sys.stderr)CODE
Docstring Block Structure3 hits · 15 pts
SeverityFileLineSnippetContext
HIGHdocs/research/AI-Trader-Analysis-Report.md809 带重试的LLM调用 实现指数退避策略处理常见错误: - RateLimitError: API速率限制 - APIError: 服务端错误 - TimeoutError: 请求超时 ArSTRING
HIGHdocs/research/AI-Trader-Analysis-Report.md994 执行交易指令 Args: symbol: 交易标的代码 - 美股: "AAPL", "MSFT", "GOOGL"等 - 加密货币: "BTCUSDT", STRING
HIGHdocs/research/AI-Trader-Analysis-Report.md1310 执行数学计算 支持基础数学运算和金融计算函数。 Args: expression: 数学表达式字符串 支持的运算: 基础运算: +, -, *, /, ** (STRING
Hyper-Verbose Identifiers12 hits · 12 pts
SeverityFileLineSnippetContext
LOWweb/src/components/trader/ModelConfigModal.tsx1151function StandardProviderConfigForm({CODE
LOWweb/src/components/charts/TradingViewChart.tsx52function TradingViewChartComponent({CODE
LOWweb/src/components/charts/ChartTabs.tsx48function getMarketTypeFromExchange(exchangeId: string | undefined): MarketType {CODE
LOWweb/src/components/common/WebCryptoEnvironmentCheck.tsx20export function WebCryptoEnvironmentCheck({CODE
LOWweb/src/components/common/HyperliquidWalletConnect.tsx115function getPreferredWalletProvider(): WalletProvider | undefined {CODE
LOWweb/src/components/common/HyperliquidWalletConnect.tsx459 async function reuseSavedExchangeIfPresent(address: string) {CODE
LOWweb/src/components/common/HyperliquidWalletConnect.tsx913 function resetTradingAuthorization() {CODE
LOWweb/src/lib/crypto.ts211export function diagnoseWebCryptoEnvironment(): WebCryptoEnvironmentInfo {CODE
LOWweb/src/lib/onboarding.ts31export function hasCompletedBeginnerOnboarding(): boolean {CODE
LOWweb/src/lib/onboarding.ts35export function markBeginnerOnboardingCompleted() {CODE
LOWweb/src/pages/TraderDashboardPage.tsx42function getExchangeDisplayNameFromList(CODE
LOWdocs/research/AI-Trader-Analysis-Report.md1809 def _get_trading_restrictions(self) -> str:STRING
Redundant / Tautological Comments3 hits · 5 pts
SeverityFileLineSnippetContext
LOW.github/workflows/pr-checks.yml336 # Check if any critical checks failed (excluding validate-pr which is advisory)COMMENT
LOW.github/workflows/scripts/calculate_coverage.py172 # Output resultsCOMMENT
LOW.github/workflows/scripts/comment_pr.py223 # Check if fork PRCOMMENT
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWapi/crypto_handler.go78 // TODO: Add validation for other chainsCOMMENT
Modern Structural Boilerplate1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/workflows/scripts/calculate_coverage.py138def set_github_output(name: str, value: str) -> None:CODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/workflows/scripts/calculate_coverage.py12CODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/workflows/scripts/calculate_coverage.py15CODE
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWapi/utils_test.go236 input: "user@example.com",CODE