Trust Assessment
spacescan 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/koba42corp/spacescan/SKILL.md:1 | |
| MEDIUM | Unpinned npm dependency version Dependency 'axios' is not pinned to an exact version ('^1.6.0'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/koba42corp/spacescan/package.json | |
| INFO | Unpinned dependency in package.json The 'axios' dependency in package.json uses a caret (^) version range, allowing minor and patch updates. While package-lock.json pins the exact version, strictly pinning dependencies in package.json (e.g., '1.6.0' instead of '^1.6.0') is a best practice for enhanced supply chain security, ensuring deterministic builds and preventing unexpected updates that could introduce vulnerabilities. Change the dependency version in package.json from "^1.6.0" to "1.6.0" to strictly pin the version. Run `npm install` afterwards to update package-lock.json if necessary. | LLM | package.json:20 |
Scan History
Embed Code
[](https://skillshield.io/report/af83122a0ccf8193)
Powered by SkillShield