tako-cli@0.3.15
Tako CLI — unified launcher for AI coding tools (Claude Code, Codex, Gemini) with multi-agent session management
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection supports a warning for agent extension/control-surface risk, not a block: risky writes are runtime or user-invoked and package-aligned, while package installation itself has no postinstall hijack. Scanner credential-exfiltration labels appear to match user API key validation/quota/model calls rather than covert theft.
Decision evidence
public snapshot- dist/index.js writes ~/.claude/settings.json statusLine to run ~/.tako/bin/tako statusline on user CLI launch
- dist/index.js can install bundled skills into project .claude/skills via explicit `tako skill install` command
- dist/index.js launches Claude/Codex/Gemini and can add dangerous flags when previously selected by user
- install.sh/install.ps1 download Bun and run `bun add tako-cli`; installer also edits shell PATH files
- package.json has no install/postinstall hook; only prepublishOnly build script
- Network calls are package-aligned: region detection, npm/Bun downloads, Tako API quota/key validation, model metadata, announcements
- No confirmed credential harvesting/exfiltration beyond user-configured provider API key validation/quota calls
- Agent/skill and client install features are documented in README and user-invoked
- No obfuscated staged payload or destructive/persistence behavior found in package files
Source & flagged code
8 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to tako-cli@0.3.15.
See all versions of tako-cli for other recorded verdicts.
- Review the evidence and your use of tako-cli@0.3.15 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.