terminal-commander@0.3.14
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 automatically writes first-party MCP configuration for detected coding agents, creating an agent extension lifecycle risk. The source shows opt-outs and CI/noninteractive guards, but no verified attack behavior that warrants blocking publication.
Decision evidence
public snapshot- The package runs a postinstall script that starts bootstrap during package installation.
- Bootstrap configures detected harnesses in install mode and forces their configuration to refresh.
- The installer can write MCP server entries to detected coding-agent configuration files, including Codex configuration.
- The configuration entries launch this package's MCP server; this is first-party agent setup, but it occurs automatically during installation.
- The postinstall skips setup when either documented opt-out variable is set or the environment is detected as CI or noninteractive.
- Inspected source supports automatic first-party MCP setup; it does not establish a separate malicious action.
Source & flagged code
11 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.14.
See all versions of terminal-commander for other recorded verdicts.
- Review the evidence and your use of terminal-commander@0.3.14 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.