terminal-commander@0.3.15
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’s postinstall can configure detected agent harnesses without an explicit setup command. This is first-party package-owned agent setup, which warrants a warning; the inspected source does not establish a concrete attack that supports blocking publication.
Decision evidence
public snapshot- The package declares a postinstall script that runs scripts/postinstall.js.
- On eligible installs, the hook calls runBootstrap in install mode; CI and noninteractive installs and explicit opt-outs skip it.
- Install mode enables automatic harness configuration, and the setup command also requests activation and automatic configuration.
- The setup path writes configurations for detected providers, so the hook can register this package’s MCP server with detected coding agents.
- The inspected setup path concerns registering this package’s own MCP server; no unrelated account action or credential transfer was established.
- The hook includes CI/noninteractive and environment opt-outs, but otherwise runs without an explicit setup command.
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.15.
See all versions of terminal-commander for other recorded verdicts.
- Review the evidence and your use of terminal-commander@0.3.15 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.