terminal-commander@0.3.10
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 active postinstall path can configure a detected coding-agent harness without a separate setup command, so this merits a warning for first-party agent setup during installation. The inspected path writes this package's MCP entry, and the source shows CI/noninteractive and opt-out guards; it does not establish a broader control-surface attack.
Decision evidence
public snapshot- The package runs a postinstall script that starts bootstrap in install mode.
- Install mode enables automatic harness configuration.
- The setup code writes a Terminal Commander MCP entry into a detected harness configuration file.
- The postinstall returns when either opt-out flag is set or the environment is identified as CI or noninteractive.
- The inspected setup path configures this package's own MCP entry; no unrelated agent-control change or credential transfer was identified.
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.10.
See all versions of terminal-commander for other recorded verdicts.
- Review the evidence and your use of terminal-commander@0.3.10 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.