Security audit
Security checks for vulnerabilities and agentic risk
The skill is a disclosed World Cup prediction CLI with optional API enrichment and local schedule caching, with no evidence of hidden persistence, exfiltration, or destructive behavior.
Install only if you are comfortable with a Chinese-localized CLI that can read an optional BALLDONTLIE API key from ~/.openclaw/openclaw.json, call that sports API when using team-list enrichment, and update its local schedule.json cache. Do not rely on the bundled schedule as authoritative without checking the data source.
The skill is described as a match predictor, but the documented behavior also includes reading a local secrets file, making authenticated outbound API requests, and reading/writing local cache data. This mismatch undermines informed consent and can hide sensitive operations behind a benign-seeming description, making misuse or over-privileged deployment more likely.
The skill declares no explicit tool scope even though the documented behavior includes network access and local file writes. Without clear permission boundaries, a host may grant broader capabilities than users expect, increasing the risk of unintended data access or modification.
This code file includes its title, usage instructions, docstrings, and runtime messages in Chinese, and there is no indication that users may choose another language or that the tool is intentionally limited to a Chinese-speaking context. Under the language/locale policy rule, forcing a specific language without user opt-in is a natural-language policy concern.
The module docstring says update will fetch the latest schedule from Netease, and fetch_schedule_from_netease also describes scraping/browser snapshot use. In practice, cmd_update never performs any network retrieval or snapshot parsing; it simply calls build_schedule_from_netease_data() and saves a static embedded schedule list.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# ── 配置 ──────────────────────────────────────────────────────────────
API_BASE = "https://api.balldontlie.io/fifa/worldcup/v1"
DATA_DIR = os.path.dirname(os.path.abspath(__file__))
SCHEDULE_CACHE = os.path.join(DATA_DIR, "schedule.json")
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# ── 配置 ──────────────────────────────────────────────────────────────
API_BASE = "https://api.balldontlie.io/fifa/worldcup/v1"
DATA_DIR = os.path.dirname(os.path.abspath(__file__))
SCHEDULE_CACHE = os.path.join(DATA_DIR, "schedule.json")
The top-level usage documentation states standings requires manual data entry, which communicates a manual workflow. However, cmd_standings explicitly loads cached schedule data and computes standings automatically via compute_group_standings(matches), so the documentation and code intent conflict.
This JSON schedule uses Chinese-only field values such as stadium names, group labels, and status markers throughout the file, with no indication that the locale is optional or user-selectable. Under the stated policy, forcing a specific language/locale without opt-in is a natural-language policy concern.
No suspicious patterns detected.