trace-mcp@3.28.0
⚠ Under reviewFramework-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 25d ago · by lpm-firewall-aiInspected lifecycle scripts, the app-update repo helper, agent-path constants, and the plugin hook manifest show first-party daemon and app update behavior rather than a foreign agent-config write or a self-dependency install chain. The citation cap blocks the required clean citation set, so the review stays unresolved instead of a warning or block.
Decision evidence
public snapshot- npm postinstall runs preflight-native, postinstall-app, and postinstall-control-plane.
- On macOS that control-plane script bootstraps the package's own launchd agent and starts its daemon, with an env and daemon.disabled opt-out.
- The app updater defaults to this package's GitHub releases API and only swaps a local trace-mcp.app.
- dist/proxy.js only defines paths under the user home for Claude, Codex, and Cursor; those names are not written by postinstall.
- Bench and replay scripts read local Claude session logs or this repo's CLAUDE.md only when those scripts are run.
- The Claude plugin hook manifest runs a package bash guard only if the user installs the plugin.
- Dependencies do not include this package name, so there is no nested lifecycle self-install.
- Required clean coverage is 16 files and the citation cap is 8, so a clean publication cannot be completed from this pass.
- Postinstall does not write Claude, Cursor, Codex, or other foreign MCP client configs.
- The launchd label and home directory are this package's own daemon, and TRACE_MCP_NO_POSTINSTALL skips the control-plane hook.
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.28.0.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.28.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.