terminal-commander@0.3.2
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 configures detected clients to use this package’s own MCP server. This fits the warning category for first-party agent extension setup, rather than establishing a publish-blockable attack.
Decision evidence
public snapshot- The package runs a postinstall hook that calls bootstrap on eligible installs.
- Install mode enables automatic harness configuration and invokes the harness writer.
- The writer targets registered MCP clients, including Cursor and Codex CLI.
- The hook skips when opted out and on CI or noninteractive installs.
- The configured MCP entry is this package’s own integration; the inspected source does not establish unrelated control-surface mutation.
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.2.
See all versions of terminal-commander for other recorded verdicts.
- Review the evidence and your use of terminal-commander@0.3.2 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.