@raolin2025/claude-code-node@3.6.17
Node.js AI Code Agent CLI - Zero dependencies, pure JavaScript, security hardened, multi-channel notifications, Telegram & QQ Bot remote programming, rich media upload, multi-account management
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found explicit CLI entrypoints and a prepublishOnly check, with no automatic install-time attack chain. Credential use is tied to the npm registry publishing workflow or notification-driven child process; no concrete malicious behavior was established.
Decision evidence
public snapshot- package.json exposes the CLI and notification daemon as explicit entrypoints; its only lifecycle hook is prepublishOnly.
- The shell tool imports a bash safety guard before providing command execution.
- The scheduler source describes task scheduling and bounded history management.
- The notification daemon passes configured API credentials to a child CLI for a user message and reads notification configuration; inspected code showed no unrelated credential recipient.
- The npm publishing tool reads the npm token and sends it to registry.npmjs.org as part of its publish workflow.
- The SSRF guard blocks loopback and private address ranges; enhanced permissions use path and URL safety checks.
Source & flagged code
11 flagged · loading sourceFindings
Affected versions and remediation
This report applies to @raolin2025/claude-code-node@3.6.17.
See all versions of @raolin2025/claude-code-node for other recorded verdicts.
- Review the evidence and your use of @raolin2025/claude-code-node@3.6.17 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.