trace-mcp@3.1.1
Framework-aware code intelligence MCP server — 60 framework integrations, 81 languages, up to 99% token reduction
AI Security Review
scanned 25d ago · by lpm-firewall-aiAutomatic installation-time daemon persistence and remote application-update behavior create a real supply-chain risk that warrants a warning. The available guards and package-scoped paths do not establish a concrete malicious attack.
Decision evidence
public snapshot- The package runs three scripts automatically after installation.
- The control-plane installer writes a per-user launch agent configuration and bootstraps it, starting a daemon on first installation.
- The application updater fetches release metadata from GitHub during installation.
- The launch-agent path is limited to this package's named service and has an opt-out sentinel.
- The updater checks for a matching checksum before replacing an existing macOS application.
Source & flagged code
10 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 trace-mcp@3.1.1.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.1.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.