Trust Assessment
farcaster-agent received a trust score of 65/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 3 findings: 1 critical, 1 high, 1 medium, and 0 low severity. Key findings include Plain text storage of private keys, Private key logged to console in example, Potential supply chain risk due to unpinned dependencies.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. The LLM Behavioral Safety layer scored lowest at 48/100, indicating areas for improvement.
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 Findings3
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| CRITICAL | Plain text storage of private keys The skill explicitly states that Farcaster account credentials, including private keys, are automatically saved to `~/.openclaw/farcaster-credentials.json` or `./credentials.json` in plain text JSON format. This poses a severe security risk as anyone with access to these files can gain full control over the associated wallet funds and Farcaster account. While the skill includes a warning, the insecure storage method is a direct vulnerability. Implement secure credential storage mechanisms, such as encrypted vaults, hardware security modules (HSMs), or environment variables managed by a secrets manager. Avoid storing private keys directly on the filesystem in plain text. | LLM | SKILL.md:68 | |
| HIGH | Private key logged to console in example The example code provided for generating a new wallet explicitly logs the newly created private key to the console (`console.log('Private Key:', wallet.privateKey);`). If a user follows this example, the private key could be captured in logs, terminal history, or visible to observers, leading to compromise of the wallet. Never log private keys or other sensitive credentials to standard output or logs. If a new wallet is generated, the private key should be immediately stored securely (e.g., encrypted) or passed directly to the next secure step without being displayed. | LLM | SKILL.md:30 | |
| MEDIUM | Potential supply chain risk due to unpinned dependencies The skill's manifest includes an `npm install` command, and the troubleshooting section suggests `npm install @farcaster/hub-nodejs@latest`. Relying on unpinned dependencies or the `@latest` tag can introduce supply chain risks, as malicious or breaking changes in upstream packages could be pulled in without explicit review, potentially compromising the skill's execution environment. Without a `package-lock.json` or specific version pinning, the exact dependencies are not guaranteed. Always use a `package-lock.json` or `yarn.lock` file to pin dependency versions. Avoid using `@latest` for critical dependencies in production environments; instead, pin to specific versions or use semantic version ranges with careful auditing. | LLM | SKILL.md:10 |
Scan History
Embed Code
[](https://skillshield.io/report/385dc4d9f44dc02b)
Powered by SkillShield