Security audit

Self-Evolved dev-tools

Security checks for vulnerabilities and agentic risk

Overview

This is a developer toolkit with expected local file and command activity, but its safety checks should not be treated as a strong security gate.

Review install.sh before running it, use dev-tk fmt --check before allowing formatting changes, and treat dev-tk review or dep as convenience checks rather than authoritative security or dependency-audit results.

SkillSpector

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access

Findings (4)

Intent-Code Divergence

Medium

Confidence: 96% confidence
Finding: The review command claims to check for null-pointer risk but unconditionally prints success and increments the P0 pass count, ignoring the scan result entirely. In a development-assurance tool, this creates a false sense of safety and can allow risky changes to pass pre-submit checks without review.

Intent-Code Divergence

Medium

Confidence: 94% confidence
Finding: The outdated-package logic is reversed: when npm returns valid JSON describing stale dependencies, the code often reports '依赖版本正常' instead of flagging updates. This can hide dependency maintenance issues and delay patching packages with known security fixes.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The skill instructs users to run `bash install.sh` directly, which is a classic unsafe installation pattern because it can execute arbitrary shell commands with the user's privileges. In a skill context, this is especially risky because the install script contents are not shown here and no warning, verification, or review step is required.

Missing User Warnings

Medium

Confidence: 93% confidence
Finding: The `fmt` command is presented as a routine operation, but formatting tools commonly rewrite files in place and may trigger broad code changes. Without an explicit warning or dry-run-first guidance, users may unintentionally modify large parts of a repository or overwrite work they did not mean to change.

Static analysis

Detected: suspicious.dangerous_exec

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: scripts/dev-tk.js:14