T09 · Insecure Skill Coding Practices
Error
- Location
scripts/scan.py:55- Finding
Unsupported “SAFE” Classification Based Only on Market Metrics
- Content
View full analysis
100000: score += 20 elif liquidity > 50000: score += 10 # Volume factor volume = token_data.get('volume24h', 0) if volume > 100000: score += 15 elif volume > 50000: score += 10 # Risk adjustments if liquidity < 10000: score -= 30 if volume < 1000: score -= 20 return max(0, min(100, score)) if __name__ == "__main__": print("[SENTRY-AI] Starting scan...") results = scan_all() print(f"Found {len(results)} pools") for token in results: risk = calculate_risk_score(token) status = "SAFE" if risk >= 70 else "RISKY" print(f"[{status}] {token['symbol']} - Risk Score: {risk}/100") print(f" Liquidity: ${token['liquidity']:,.0f}") print(f" URL: {token['url']}") print() ``` ### Technical Analysis The scanner assigns an initial score of 50 and adjusts it using only reported liquidity and 24-hour trading volume. A score of 70 or higher is then presented as `SAFE`. These metrics do not establish smart-contract safety. The implementation does not examine: - Mint or freeze authorities - Owner or administrator privileges - Transfer restrictions or honeypot behavior - Upgradeability and proxy administration - Holder concentration - Liquidity ownership or lock status - Sellability and fee manipulation - Contract source code or bytecode - Token supply manipulation - Wash trading or artificially generated volume Liquidity and volume can be su ...[truncated 1471 chars]- Remediation
View remediation