Security audit
Security checks across malware telemetry and agentic risk
This is a paid trade-data query skill, but it needs review because it handles API keys, account top-ups, and an automatic version check with persistent local writes.
Install only if you are comfortable with this skill using a paid UpKuaJing account, storing an API key in a local plaintext file, creating top-up payment URLs when you ask it to, and making an automatic version-check request during API use. Do not share terminal output that may include `~/.upkuajing/.env`, and review charges before confirming any query or top-up action.
### **API Key Not Set** First check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY; If UPKUAJING_API_KEY is not set, prompt the user to choose: 1. User has one: User provides it (manually add to ~/.upkuajing/.env file) 2. User doesn't have one: You can apply using the interface (`auth.py --new_key`), the new key will be automatically saved to ~/.upkuajing/.env Wait for user selection;
First check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY; If UPKUAJING_API_KEY is not set, prompt the user to choose: 1. User has one: User provides it (manually add to ~/.upkuajing/.env file) 2. User doesn't have one: You can apply using the interface (`auth.py --new_key`), the new key will be automatically saved to ~/.upkuajing/.env Wait for user selection; ### **Account Top-up**
"envFilePath": str(env_file)
}
# 保存到 .env 文件
try:
with open(env_file, 'w', encoding='utf-8') as f:
f.write(f"{API_KEY_ENV}={api_key}\n")except IOError as e:
return {
"success": False,
"message": f"API密钥申请成功，但保存到 .env 文件失败：{str(e)}。\n请手动设置环境变量 {API_KEY_ENV}。",
"envFilePath": str(env_file)
}httpx>=0.23.0
65/65 vendors flagged this skill as clean.
Detected: suspicious.exposed_secret_literal