terminal-commander@0.3.1
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 performs first-party MCP harness setup, with opt-out and CI/non-interactive guards. This warrants a warning for lifecycle-driven agent configuration changes, but the inspected source does not establish a broader control-surface attack or other concrete malicious behavior.
Decision evidence
public snapshot- The package runs scripts/postinstall.js after installation.
- On interactive installs without the opt-out flags, postinstall calls runBootstrap in install mode.
- Install mode enables automatic configuration and writes this package's MCP server entry to detected harness configuration.
- The JSON writer merges the named server entry while preserving other server entries.
- The postinstall path skips when opted out or when CI/non-interactive detection applies.
- The inspected behavior configures this package's own MCP integration; no unrelated credential transfer or dependency approval change 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.1.
See all versions of terminal-commander for other recorded verdicts.
- Review the evidence and your use of terminal-commander@0.3.1 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.