Trust Assessment
qwen-image-plus-sophnet received a trust score of 73/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 2 findings: 0 critical, 2 high, 0 medium, and 0 low severity. Key findings include Command Injection via API Key, Command Injection via API Key (Polling Request).
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on February 14, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings2
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| HIGH | Command Injection via API Key The `API_KEY` variable, which can be set by the user via command-line argument (`--api-key`) or environment variable (`SOPHNET_API_KEY`), is directly embedded into `curl` command headers without sufficient sanitization. This allows for command injection if the API key value contains shell metacharacters such as `$(command)` or backticks. An attacker could craft a malicious API key to execute arbitrary commands on the host system. Sanitize or validate the `API_KEY` variable to ensure it only contains expected characters (e.g., alphanumeric, hyphens). Alternatively, use a more robust method for passing sensitive data to `curl` that prevents shell interpretation, such as reading from a file descriptor or using a library that handles escaping properly. For shell scripts, a common mitigation is to validate the input against a strict regex pattern for API keys. | LLM | scripts/generate_image.sh:146 | |
| HIGH | Command Injection via API Key (Polling Request) The `API_KEY` variable, which can be set by the user via command-line argument (`--api-key`) or environment variable (`SOPHNET_API_KEY`), is directly embedded into `curl` command headers during the polling phase without sufficient sanitization. This allows for command injection if the API key value contains shell metacharacters such as `$(command)` or backticks. An attacker could craft a malicious API key to execute arbitrary commands on the host system. Sanitize or validate the `API_KEY` variable to ensure it only contains expected characters (e.g., alphanumeric, hyphens). Alternatively, use a more robust method for passing sensitive data to `curl` that prevents shell interpretation, such as reading from a file descriptor or using a library that handles escaping properly. For shell scripts, a common mitigation is to validate the input against a strict regex pattern for API keys. | LLM | scripts/generate_image.sh:168 |
Scan History
Embed Code
[](https://skillshield.io/report/dd768aa6328e0350)
Powered by SkillShield