trace-mcp@3.6.0
Framework-aware code intelligence MCP server — 87 framework integrations, 81 languages, 40–50% fewer tokens on average
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a real install-time persistence and update surface, but the inspected source does not establish credential theft, third-party agent-control mutation, or other concrete malicious behavior. It warrants a warning as a first-party lifecycle risk.
Decision evidence
public snapshot- The package runs three scripts automatically in postinstall.
- The postinstall hook writes a per-user launcher configuration and executable shim.
- On macOS it creates a launchd job with RunAtLoad and KeepAlive, starting a persistent local daemon.
- The install hook fetches a release from GitHub and can replace an installed application; its updater can reinstall trace-mcp globally.
- No dependency on trace-mcp itself appears in package.json.
- The app update path requires an existing macOS app and checks a release checksum.
- No source evidence shows secret collection, exfiltration, or mutation of third-party AI-client settings during install.
Source & flagged code
14 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 unpkgPackage source references child process execution.
scripts/count-advertised-tools.mjsFindings
Affected versions and remediation
This report applies to trace-mcp@3.6.0.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.6.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.