ClawHub
Back to skill

Security audit

全国天气预报查询 - 聚合数据

Security checks for vulnerabilities and agentic risk

Overview

This is a straightforward weather lookup skill, with ordinary API-key handling risks users should manage carefully.

Install only if you are comfortable providing a Juhe weather API key. Prefer the JUHE_WEATHER_KEY environment variable, avoid passing the key on the command line, do not commit scripts/.env, and consider changing the Juhe endpoints to HTTPS if supported.

SkillSpector

Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Credential Access

High
Category
Privilege Escalation
Content
# 方式一：环境变量（推荐）
export JUHE_WEATHER_KEY=你的AppKey

# 方式二：.env 文件
echo "JUHE_WEATHER_KEY=你的AppKey" > scripts/.env

# 方式三：命令行传入
Confidence
88% confidence
Finding
The documentation recommends writing the API key to `scripts/.env` and also passing it on the command line. Storing secrets in a project subdirectory increases the risk of accidental inclusion in source control or exposure to other tooling, and CLI arguments can be visible in shell history, process listings, logs, or telemetry.

Credential Access

High
Category
Privilege Escalation
Content
export JUHE_WEATHER_KEY=你的AppKey

# 方式二：.env 文件
echo "JUHE_WEATHER_KEY=你的AppKey" > scripts/.env

# 方式三：命令行传入
python scripts/weather.py --key 你的AppKey 北京
Confidence
93% confidence
Finding
The explicit example `echo "JUHE_WEATHER_KEY=你的AppKey" > scripts/.env` normalizes persisting a credential in a potentially repository-adjacent path. In a skill/package context, this makes accidental secret leakage more likely through version control, backups, or file reads by unrelated components.

Static analysis

No suspicious patterns detected.