Trust Assessment
token-launcher received a trust score of 86/100, placing it in the Mostly Trusted category. This skill has passed most security checks with only minor considerations noted.
SkillShield's automated analysis identified 3 findings: 0 critical, 0 high, 2 medium, and 0 low severity. Key findings include Missing required field: name, Unpinned npm dependency version, Unpinned Dependency in package.json.
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 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Security Findings3
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| MEDIUM | Missing required field: name The 'name' field is required for claude_code skills but is missing from frontmatter. Add a 'name' field to the SKILL.md frontmatter. | Static | skills/clawd800/token-launcher/SKILL.md:1 | |
| MEDIUM | Unpinned npm dependency version Dependency 'viem' is not pinned to an exact version ('^2.45.1'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/clawd800/token-launcher/scripts/package.json | |
| INFO | Unpinned Dependency in package.json The 'viem' dependency in 'scripts/package.json' uses a caret (^) version specifier, allowing minor and patch updates. While common, exact version pinning is recommended for security-critical applications to ensure deterministic builds and prevent unexpected changes from upstream dependencies that could introduce vulnerabilities. Pin the 'viem' dependency to an exact version (e.g., '2.45.1') to ensure deterministic builds and prevent unexpected updates. Regularly audit and manually update dependencies. | LLM | scripts/package.json:6 |
Scan History
Embed Code
[](https://skillshield.io/report/49b8485ce92c607d)
Powered by SkillShield