Security Audit
ignisign-automation
github.com/ComposioHQ/awesome-claude-skillsTrust Assessment
ignisign-automation received a trust score of 93/100, placing it in the Trusted category. This skill has passed all critical security checks and demonstrates strong security practices.
SkillShield's automated analysis identified 1 finding: 0 critical, 0 high, 1 medium, and 0 low severity. Key findings include Unpinned dependency in manifest.
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 17, 2026 (commit 99e2a295). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Security Findings1
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| MEDIUM | Unpinned dependency in manifest The skill's manifest declares a dependency on the 'rube' MCP without specifying a version constraint. This means the skill could automatically use any version of the 'rube' MCP, including future versions that might introduce vulnerabilities, breaking changes, or malicious behavior. This lack of pinning creates a supply chain risk, as the skill's security posture is entirely dependent on the ongoing integrity and security of all future 'rube' MCP releases. Specify a version range for the 'rube' MCP dependency in the manifest (e.g., `"rube": ">=1.0.0,<2.0.0"`) to ensure compatibility and prevent unexpected behavior or security issues from future updates. Regularly review and update the pinned version as new, secure versions become available. | Static | Manifest (frontmatter JSON) |
Scan History
Embed Code
[](https://skillshield.io/report/97fe46e713965bc3)
Powered by SkillShield