Trust Assessment
clawdzap received a trust score of 82/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 via Missing Lockfile.
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 Findings4
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| MEDIUM | Unpinned npm dependency version Dependency 'nostr-tools' is not pinned to an exact version ('^2.1.0'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/guilh00009/clawdzap/package.json | |
| MEDIUM | Unpinned Dependencies via Missing Lockfile The `package.json` file specifies dependencies using caret (`^`) ranges, which allow for minor and patch updates. Crucially, a `package-lock.json` file is not provided. This means that `npm install` is not deterministic and could resolve to different versions of dependencies (and their transitive dependencies) over time. A malicious update to a dependency or a transitive dependency could introduce vulnerabilities or unwanted behavior without explicit review, increasing supply chain risk. Generate and commit a `package-lock.json` file to ensure deterministic dependency resolution. For critical security-sensitive libraries, consider pinning exact versions (e.g., `"nostr-tools": "2.1.0"`) or using tilde ranges (`~`) for more controlled updates. | LLM | package.json:5 | |
| 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/guilh00009/clawdzap/package.json | |
| LOW | Sensitive Secret Key Stored on Filesystem The skill generates and stores a Nostr secret key (`sk`) in a JSON file (`~/.clawdzap_keys.json`) on the local filesystem. While this is necessary for the skill's intended functionality (identity management for Nostr communication), storing sensitive cryptographic keys on disk creates a potential data exfiltration risk. If an attacker gains local filesystem access to the agent's environment, they could read this file and compromise the agent's Nostr identity, allowing them to impersonate the agent or decrypt private messages. Implement robust access controls for `~/.clawdzap_keys.json` (e.g., `chmod 600`) where possible, although cross-platform enforcement can be challenging. Consider alternative secure storage mechanisms if the environment supports them (e.g., OS-level keyrings, secure enclaves). Educate users about the sensitivity of this file and the importance of protecting their agent's environment. | LLM | send.js:15 |
Scan History
Embed Code
[](https://skillshield.io/report/fe22b296da0f1c72)
Powered by SkillShield