registry / claude-code-infinite / 1.0.22
claude-code-infinite@1.0.22
⚠ Under reviewWrapper for Claude Code CLI
Static Scan Results
scanned 18d ago · by rust-scannerStatic analysis completed at 65.0% confidence. No malicious behavior was detected; 11 low-signal pattern(s) were surfaced and cleared.
Static reason
No blocking static signals were detected.
Decision evidence
public snapshotBehavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
4 flaggeddist/resume-repair-file.jsView file
4import { randomUUID } from "node:crypto";
L5: import { execFileSync } from "node:child_process";
L6: /** Possible writers include Claude binaries and JS runtimes; uncertainty skips repair. */
High
Child Process
Package source references child process execution.
dist/resume-repair-file.jsView on unpkg · L4dist/cli-main.jsView file
64platform === "win32"
L65: ? exec(`${command} "${url}"`, { shell: "cmd.exe" })
L66: : exec(`${command} "${url}"`);
High
443// native login and sends its own OAuth bearer to the local base URL.
L444: const child = spawn("claude", childArgs, {
L445: env: claudeChildEnv(process.env, `http://127.0.0.1:${proxy.port}`),
L446: stdio: "inherit",
High
Findings
4 High2 Medium5 Low
HighChild Processdist/resume-repair-file.js
HighShelldist/cli-main.js
HighSame File Env Network Executiondist/cli-main.js
HighSemantic Analysis Limiteddist/cc-request.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to claude-code-infinite@1.0.22.
See all versions of claude-code-infinite for other recorded verdicts.
- Review the evidence and your use of claude-code-infinite@1.0.22 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.