trace-mcp@3.35.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 13d ago · by lpm-firewall-aiThe source facts inspected support package-aligned installation and development behavior, while the scanner’s similarity labels do not establish malicious conduct. No concrete attack surface was confirmed.
Decision evidence
public snapshot- The install hook runs package-owned preflight, app-update, and control-plane scripts; the inspected preflight checks bundled native files, while the control-plane script manages trace-mcp’s own launcher.
- The flagged bundle locations define paths for Claude, Codex, and other agent data; the inspected script locations concern session replay and token-count benchmarking.
- The flagged scripts are development utilities for screenshots, upgrade checks, wire fixtures, throughput and session benchmarks, documentation generation, and daemon performance.
- No inspected source established credential theft, unrelated agent-control writes, dependency approval expansion, or another concrete attack.
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.35.0.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.35.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.