terminal-commander@0.3.5
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 package has an automatic postinstall path that modifies detected coding-agent configuration to add its own MCP server. Its scope and guards support a lifecycle setup warning, while inspected source does not establish an unconsented broad control-surface attack.
Decision evidence
public snapshot- The npm postinstall hook runs the setup bootstrap during eligible interactive installs.
- The install bootstrap automatically configures detected harnesses and forces its configuration path.
- The writer adds this package's MCP server configuration to supported harness files.
- The hook skips when either opt-out is set and skips CI or noninteractive installs.
- Harness configuration is limited to detected providers, and the written entry launches this package's own MCP server.
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.5.
See all versions of terminal-commander for other recorded verdicts.
- Review the evidence and your use of terminal-commander@0.3.5 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.