trace-mcp@3.37.4
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 8d ago · by lpm-firewall-aiThe active postinstall hook performs package-aligned verification, update, and daemon setup. The required agent-related locations resolve to path definitions and explicitly invoked local analysis scripts; no malicious behavior was identified.
Decision evidence
public snapshot- package.json runs native preflight, the app updater, and the control-plane helper during postinstall.
- The installer verifies native binaries and configures trace-mcp’s own launcher and daemon files; the app update source defaults to the project’s release repository.
- The designated bundle locations define home-directory agent paths; the other designated scripts analyze repository instructions or local session logs, with session IDs removed from saved results.
- The flagged scripts describe screenshot capture, update verification, fixture recording, documentation generation, and performance or model benchmarks; they are not in the postinstall chain.
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.4.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.37.4 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.