T08 · Insecure Dependencies
- Location
SKILL.md:24- Finding
Unpinned Third-Party Security Scanner Dependency
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a disclosed local Slither wrapper, but its audit script can turn failed scans into clean-looking reports.
Install and run this only in an isolated environment, preferably with a pinned Slither version. Do not rely on a clean report unless you confirm Slither actually completed successfully; failed compilation, missing tools, or malformed output may be reported as zero findings.
SKILL.md:24Unpinned Third-Party Security Scanner Dependency
slither-audit.py:44Slither Execution Failures Are Reported as Clean Audit Results
The skill instructs the user to run shell commands (pip install slither-analyzer, python3 slither-audit.py ...) and therefore has shell-execution capability, but it does not declare any permissions or allowed-tools scope in its metadata. Missing tool scoping weakens least-privilege controls and can allow an agent runtime to grant broader command execution than reviewers or policy engines expect.
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
def run_slither(contract_path):
"""Run slither static analysis."""
try:
result = subprocess.run(
["slither", contract_path, "--json", "-"],
capture_output=True,
text=True,
No suspicious patterns detected.