Trust Assessment
edge-tts received a trust score of 74/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 3 findings: 0 critical, 1 high, 2 medium, and 0 low severity. Key findings include Unpinned npm dependency version, Unpinned dependencies in package.json, Execution of `npm install` during skill installation.
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 Findings3
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| HIGH | Execution of `npm install` during skill installation The `install.sh` script explicitly executes `npm install --production`. This command can execute arbitrary code via `preinstall`, `install`, or `postinstall` scripts defined in the `package.json` of direct or transitive dependencies. This is a common vector for supply chain attacks, where a compromised dependency could lead to arbitrary code execution on the host system during skill installation, potentially allowing an attacker to gain control or exfiltrate data. Implement robust supply chain security measures, including auditing all dependencies for known vulnerabilities and suspicious behavior. Consider using tools that verify package integrity and restrict network access during installation. If possible, containerize installations to isolate potential threats. | LLM | install.sh:10 | |
| MEDIUM | Unpinned npm dependency version Dependency 'node-edge-tts' is not pinned to an exact version ('^1.2.9'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/i3130002/edge-tts/scripts/package.json | |
| MEDIUM | Unpinned dependencies in package.json The `package.json` file specifies dependencies (`node-edge-tts`, `commander`) using caret (`^`) ranges, allowing minor and patch updates. While `package-lock.json` pins exact versions for reproducibility, relying on `^` ranges in `package.json` can introduce supply chain risks if new versions of these packages introduce vulnerabilities or malicious code. An attacker could publish a malicious update to a dependency, which would then be pulled in during a future `npm install` if the `package-lock.json` is not strictly enforced or updated. Pin dependencies to exact versions (e.g., `"node-edge-tts": "1.2.9"`) to ensure consistent and secure builds. Regularly audit and update dependencies after careful review. | LLM | scripts/package.json:7 |
Scan History
Embed Code
[](https://skillshield.io/report/d6228ed7e5f77afa)
Powered by SkillShield