terminal-commander@0.3.3
Terminal Commander: local MCP-operated terminal/file signal channel with native Linux, Windows, and macOS packages.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe postinstall hook automatically adds this package's own MCP integration to detected agent configurations, a guarded first-party extension setup that merits warning under policy. I found no separate concrete attack behavior in the inspected paths.
Decision evidence
public snapshot- The package runs scripts/postinstall.js automatically after installation.
- On interactive, non-CI installs without either opt-out flag, the hook invokes bootstrap in install mode.
- Install mode enables automatic harness configuration, which writes this package's MCP server entry to detected agent configurations.
- The configured provider set includes Cursor, Codex CLI, Claude Code, Claude Desktop, and OMP.
- The manual setup command uses CLI mode and refreshes the package's named entry.
- The hook skips when TC_SKIP_BOOTSTRAP or TC_NO_AUTO_SETUP is set, and skips CI or noninteractive installs.
- The setup writes concern this package's own MCP server entry, consistent with its stated integration purpose.
Source & flagged code
16 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to terminal-commander@0.3.3.
See all versions of terminal-commander for other recorded verdicts.
- Review the evidence and your use of terminal-commander@0.3.3 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.