trace-mcp@3.26.0
Framework-aware code intelligence MCP server — 88 framework integrations, 81 languages, 72.7% fewer input tokens to review a pull request, comprehension at parity
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is an automatic lifecycle persistence mechanism with meaningful install-time side effects, so it warrants a warning. The inspected behavior is package-aligned and lacks a concrete malicious chain or self-dependency.
Decision evidence
public snapshot- The package runs three scripts automatically during postinstall.
- Postinstall creates a package-owned launcher and records paths under the user's home directory.
- On macOS, postinstall writes and bootstraps a persistent LaunchAgent that starts the local daemon.
- A conditional postinstall updater contacts GitHub to replace legacy trace-mcp app bundles.
- No runtime dependency on trace-mcp itself was found.
- The control-plane script only manages trace-mcp-owned paths and does not modify Claude or Codex configuration.
- The legacy app updater verifies a SHA-256 checksum and uses Gatekeeper before replacing an app.
- No credential harvesting or secret exfiltration was identified in the inspected lifecycle scripts.
Source & flagged code
26 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.26.0.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.26.0 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.