trace-mcp@3.24.0
Framework-aware code intelligence MCP server — 87 framework integrations, 81 languages, 72.7% fewer input tokens to review a pull request, comprehension at parity
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has a concrete automatic lifecycle and persistence surface, so it should not be treated as clean. Static inspection found no self-dependency, foreign AI-agent configuration mutation, or credential exfiltration that would justify a block.
Decision evidence
public snapshot- The package runs three scripts automatically after installation.
- The postinstall script writes a per-user launchd service with RunAtLoad and KeepAlive, then bootstraps it.
- The install hook can fetch a release archive and replace an existing trace-mcp application bundle.
- Install-time persistence and updater behavior create a concrete lifecycle risk.
- No runtime dependency refers to trace-mcp itself.
- The reviewed installer targets trace-mcp-owned paths and service names, not Claude, Codex, or other agent configuration.
- The updater verifies a SHA-256 checksum before applying an archive.
- No credential harvesting or secret exfiltration was found in the inspected install scripts.
Source & flagged code
17 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.24.0.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.24.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.