trace-mcp@3.37.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 9d ago · by lpm-firewall-aiThe install behavior configures Trace's own launcher and daemon, while the flagged auxiliary files implement benchmarks, update checks and documentation or fixture generation. Runtime telemetry is package-aligned and has effective environment and configuration opt-outs; no concrete attack chain was found.
Decision evidence
public snapshot- The postinstall chain runs a native-code preflight and Trace's app and control-plane setup scripts; preflight asks codesign to verify native modules.
- The control-plane hook writes Trace's launcher state and may register Trace's own macOS daemon; a daemon-disabled marker skips registration. The app updater queries GitHub release metadata and selects Trace-named bundles.
- The indicated bundle locations construct standard agent-directory paths. The associated scripts benchmark CLAUDE.md and AGENTS.md text and read local Claude session logs.
- Flagged auxiliary scripts perform screenshot, documentation, fixture, report, update-check and benchmark work, with outputs directed to package assets, fixtures or reports.
- Server initialization announces and sends a package-usage event to Google Analytics with an install identifier and device and usage fields; environment and config options disable it.
- The postinstall hook automatically sets up user-level launcher files and can register a macOS LaunchAgent.
- Runtime initialization sends usage telemetry by default, including a persistent install identifier and device and usage metadata; environment and config opt-outs are present.
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.37.0.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.37.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.