trace-mcp@1.48.1
Framework-aware code intelligence MCP server — 60 framework integrations, 81 languages, up to 99% token reduction
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe code establishes first-party background-service persistence during postinstall, but the reviewed evidence does not show credential theft, foreign agent-control writes, or a concrete hostile payload. This is a guarded lifecycle risk rather than proven malware.
Decision evidence
public snapshot- The package runs three scripts automatically at postinstall.
- The control-plane script writes a macOS LaunchAgent and invokes its bootstrap path, starting the package daemon on first install.
- The postinstall updater contacts GitHub Releases and requires a checksum asset before updating an existing app.
- The service is scoped to trace-mcp paths and has an environment-based opt-out.
- No credential collection, foreign AI-agent configuration write, or secret transmission was identified in the inspected lifecycle code.
Source & flagged code
9 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@1.48.1.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@1.48.1 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.