Trust Assessment
blinko received a trust score of 67/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 5 findings: 0 critical, 1 high, 2 medium, and 2 low severity. Key findings include Unsafe deserialization / dynamic eval, Unpinned npm dependency version, Node lockfile missing.
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 Findings5
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| HIGH | Skill requires and uses WALLET_PRIVATE_KEY for on-chain transactions The 'blinko' skill, specifically the `play-blinko.js` script, requires the `WALLET_PRIVATE_KEY` environment variable to sign messages and execute on-chain transactions that spend real ETH. While this is necessary for the skill's stated purpose of playing Blinko, it grants the skill direct and complete control over the associated cryptocurrency wallet. Any compromise of the skill's execution environment, its dependencies, or the host LLM could lead to unauthorized fund transfers. The `SKILL.md` explicitly warns about this significant financial risk. Users should be fully aware of the financial risks associated with providing a private key. It is strongly recommended to use a dedicated hot wallet with minimal funds for this skill. Implement robust security measures for the execution environment. Consider exploring alternative authentication methods or hardware wallet integration for enhanced security if the underlying platform supports it. | LLM | scripts/play-blinko.js:40 | |
| MEDIUM | Unsafe deserialization / dynamic eval Decryption followed by code execution Remove obfuscated code execution patterns. Legitimate code does not need base64-encoded payloads executed via eval, encrypted-then-executed blobs, or dynamic attribute resolution to call system functions. | Manifest | skills/tolibear/blinko/scripts/play-blinko.js:18 | |
| MEDIUM | Unpinned npm dependency version Dependency 'ethers' is not pinned to an exact version ('^6.0.0'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/tolibear/blinko/package.json | |
| 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/tolibear/blinko/package.json | |
| LOW | Unpinned 'ethers' dependency The `package.json` specifies the `ethers` dependency with a caret (`^`) operator: `"ethers": "^6.0.0"`. This allows for automatic updates to new minor and patch versions. While `ethers` is a reputable and widely used library, unpinned dependencies can theoretically introduce vulnerabilities if a new version contains a flaw or breaking change. Pinning to an exact version (e.g., `"ethers": "6.x.y"`) and committing a lockfile (`package-lock.json`) would provide stronger supply chain integrity and ensure deterministic builds. Pin the `ethers` dependency to an exact version (e.g., `"ethers": "6.11.1"`) and ensure `package-lock.json` is committed to the repository. Regularly review and manually update dependencies to benefit from security patches while maintaining control over version changes. | LLM | package.json:7 |
Scan History
Embed Code
[](https://skillshield.io/report/a5575fc27411c296)
Powered by SkillShield