Trust Assessment
fastclaw-relay received a trust score of 81/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 4 findings: 0 critical, 0 high, 2 medium, and 2 low severity. Key findings include Unpinned npm dependency version, Node lockfile missing, Unpinned dependencies 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
Behavioral Risk Signals
Security Findings4
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| MEDIUM | Unpinned npm dependency version Dependency 'convex' is not pinned to an exact version ('^1.28.2'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/jamesalmeida/fastclaw-relay/package.json | |
| MEDIUM | Unpinned dependencies in package.json The `package.json` file specifies dependencies using caret (`^`) ranges (e.g., `^1.28.2`). This allows minor and patch version updates automatically, which could introduce vulnerabilities or breaking changes without explicit review. For security-sensitive applications, it is best practice to pin exact versions or use a lock file to ensure deterministic builds. Pin exact versions for all dependencies (e.g., `"convex": "1.28.2"`) or ensure a `package-lock.json` or `yarn.lock` file is committed and used for deterministic dependency resolution. | LLM | package.json:20 | |
| LOW | Node lockfile missing package.json is present but no lockfile was found (package-lock.json, pnpm-lock.yaml, or yarn.lock). Commit a lockfile for deterministic dependency resolution. | Dependencies | skills/jamesalmeida/fastclaw-relay/package.json | |
| LOW | Gateway token transmitted over unencrypted local WebSocket The `gatewayToken` is a sensitive credential read from local configuration and environment variables. It is then transmitted over an unencrypted WebSocket connection (`ws://127.0.0.1:18789`) to the local OpenClaw Gateway. While this communication is restricted to the loopback interface, an attacker with local machine access or a compromised local Gateway could potentially intercept this token. Using `wss://` with proper certificate validation, even for loopback, or a more secure Inter-Process Communication (IPC) mechanism, would enhance security. Implement encrypted communication (e.g., `wss://` with self-signed or trusted certificates) for the local Gateway WebSocket connection, or explore alternative secure IPC mechanisms for transmitting sensitive credentials. | LLM | scripts/relay.mjs:104 |
Scan History
Embed Code
[](https://skillshield.io/report/2e02275492624918)
Powered by SkillShield