polymarket-social-trends-trader 安全扫描报告 — 低风险 | ClawSafe

12 /100

polymarket-social-trends-trader

Trades Polymarket prediction markets on social trend indicators using conviction-based sizing with ideological motivation correction and US legislative calendar bias

A legitimate Polymarket trading strategy with fully documented behavior, safe paper-trading defaults, and no hidden functionality — minor concern only around unpinned dependency.

技能名称polymarket-social-trends-trader

分析耗时32.9s

引擎pi

✓

可以安装

Pin simmer-sdk to a specific version (e.g., simmer-sdk==x.y.z) to eliminate supply-chain risk. Otherwise, safe to use as documented.

安全发现 1 项

严重性	安全发现	位置
低危	Unpinned simmer-sdk dependency 供应链 clawhub.json declares 'simmer-sdk' without a version constraint. pip install will resolve to the latest available version at install time, which could introduce unexpected behavior if a breaking or malicious version is released. `"pip": ["simmer-sdk"]` → Pin to a specific version: "simmer-sdk>=x.y.z,<x.y+1.0" or exact pin "simmer-sdk==x.y.z". Check PyPI for current version and pin accordingly.	`clawhub.json:6`

资源类型	声明权限	推断权限	状态	证据
网络访问	`READ`	`READ`	✓ 一致	Uses SimmerClient from simmer-sdk to query Polymarket API for market discovery a…
环境变量	`READ`	`READ`	✓ 一致	Reads SIMMER_API_KEY and SIMMER_* tunable env vars — all declared in SKILL.md an…
命令执行	`NONE`	`NONE`	—	No subprocess, no os.system, no shell execution found
文件系统	`NONE`	`NONE`	—	No file reads or writes found; only env vars via os.environ
剪贴板	`NONE`	`NONE`	—	Not accessed
浏览器	`NONE`	`NONE`	—	Not accessed
数据库	`NONE`	`NONE`	—	Not accessed
技能调用	`NONE`	`NONE`	—	No nested skill invocations

目录结构

3 文件 · 26.0 KB · 567 行

Python 1f · 366L Markdown 1f · 128L JSON 1f · 73L

├─ 📋 clawhub.json JSON 73L · 1.2 KB

├─ 📝 SKILL.md Markdown 128L · 7.2 KB

└─ 🐍 trader.py Python 366L · 17.6 KB

依赖分析 1 项

包名	版本	来源	已知漏洞	备注
`simmer-sdk`	`unpinned`	pip (PyPI)	否	No version constraint declared in clawhub.json — install-time resolution risk

安全亮点

✓ Paper trading is the safe default (venue="sim") — no real financial risk without explicit --live flag

✓ No shell execution, subprocess, or os.system calls

✓ No sensitive file access (~/.ssh, ~/.aws, .env, credentials files)

✓ No network requests to raw IPs or external endpoints outside the Simmer SDK

✓ No base64 encoding, eval, or obfuscation patterns

✓ No credential harvesting beyond the declared SIMMER_API_KEY

✓ No hidden functionality — code and documentation are consistent

✓ No auto-start or cron configuration (autostart: false, cron: null)

✓ All environment variable access is via documented tunable parameters (SIMMER_*)