Node Auto Debugger

Scan Node.js/Express/Next.js projects for bugs, security issues, and anti-patterns. Use when debugging a Node.js web app, running code audits, fixing client-...

This tool is internally coherent and appears to do what it says, but it will read your project's source files (including package.json and any plaintext secrets), produce a report on disk, and — if you use the --build option — run npm run build which executes the project's build scripts. Only run it on projects you trust or run it inside an isolated environment (container/VM) when scanning untrusted code. Before sharing the generated AUTO-DEBUG-REPORT.md, review it for any sensitive data it may have flagged. Avoid passing a very large or root path (e.g., '/') as <project-dir> to prevent scanning unintended parts of your filesystem. If you only want static checks, run the script without the --build flag and inspect the script source yourself to confirm behavior.

Type: OpenClaw Skill Name: node-auto-debugger Version: 1.0.0 The node-auto-debugger skill performs automated auditing of Node.js projects, including scanning for hardcoded secrets and private keys. It is classified as suspicious because it implements high-risk capabilities in `scripts/auto-debug.js`, specifically recursive file system access and the execution of arbitrary shell commands via `npm run build`. While these functions are aligned with the tool's stated purpose of debugging and build verification, they represent a significant attack surface for code execution if the agent is directed to run the tool on an untrusted project directory.