Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Solidity Guardian
v1.0.3Smart contract security analysis skill. Detect vulnerabilities, suggest fixes, generate audit reports. Supports Hardhat/Foundry projects. Uses pattern matchi...
⭐ 0· 719·2 current·2 all-time
by@aviclaw
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (Solidity security analysis) aligns with the provided analyzer.js and slither-integration.js which implement pattern-based checks and optional Slither integration. This is coherent for an on-repo static scanner + optional Slither. However, the SKILL.md references scripts/files that are not present (analyze.js, reporter.js, hardhat-plugin), indicating the documentation and exported API may not match the shipped code.
Instruction Scope
Instructions are about analyzing local smart-contract source and generating reports, which is appropriate. They do not request secrets. Concerns: SKILL.md examples call node skills/solidity-guardian/analyze.js and require('./reporter') / hardhat plugin paths that are not in the file manifest. The runtime code (slither-integration.js and analyzer.js) will read project files, create a temporary JSON in /tmp, and may invoke system commands (slither, pip). Reading project source is expected; invoking installers is more intrusive and should be run intentionally.
Install Mechanism
No formal install spec is declared (instruction-only), which is lowest-risk. The included slither-integration.js, however, can auto-install Slither by running pipx/pip3/python3 -m pip commands via execSync. That behavior is optional (triggered by --install-slither) but will execute network installs and may modify the environment. This is expected for integrating Slither but is higher-risk than a pure JS-only tool and should be run in a controlled environment.
Credentials
The skill declares no required environment variables, credentials, or config paths and the code does not reference secrets or unexpected environment variables. The behavior is proportional to its purpose (analyzing local source).
Persistence & Privilege
The skill does not request always:true and does not modify other skills or global agent configuration. The only notable side-effect is the optional installation of Slither (system-level pip installs) and writing a temporary file under /tmp, both of which are expected for the described functionality.
What to consider before installing
This skill appears to implement a Solidity static scanner and optional Slither integration, but there are discrepancies you should resolve before running it:
- Documentation vs code mismatches: SKILL.md examples reference analyze.js, reporter.js, and a hardhat plugin that are not present in the package (the code contains analyzer.js and slither-integration.js). Confirm which entrypoints to run and whether analyzer exports the functions the integration expects (analyzeDirectory/analyzeFile/generateMarkdownReport). Running mismatched commands will fail or behave unexpectedly.
- Optional installer executes pip/pipx: slither-integration.js can auto-install Slither by running pipx/pip3/python3 -m pip via execSync. That will perform network installs and may change your system Python environment — run this only in an isolated or CI environment (container, VM) if you choose to auto-install.
- Review the code yourself (or have a developer do so) before running: analyzer.js parses local Solidity files and slither-integration.js executes shell commands. There are no obvious exfiltration endpoints, but you should still audit exported functions, ensure no unexpected network calls are added, and test in a sandbox.
- Practical steps before using:
1) Open analyzer.js and confirm it exports the functions the integrator and examples expect.
2) Run the tool on a small, non-sensitive sample project first. Do not use --install-slither on a host with sensitive packages; prefer pre-installing Slither in an isolated environment.
3) If you plan to integrate with CI, vendor or pin the Slither installation steps and review those commands.
Given the mismatches and the installer behavior, treat this skill with caution until these inconsistencies are resolved or you run it in a controlled environment.Like a lobster shell, security has layers — review code before you run it.
latestvk971sgec0e0n1w4bchfc2wakes81607d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
