trace-mcp@3.23.2
Framework-aware code intelligence MCP server — 87 framework integrations, 81 languages, 72.8% fewer input tokens to review a pull request, comprehension at parity
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has a concrete automatic persistence and remote-update surface, but the inspected behavior is scoped to its own launcher and application rather than a foreign AI-agent configuration. This warrants a warning rather than a malware block under the stated policy.
Decision evidence
public snapshot- The automatic postinstall hook runs two state-changing installers.
- On installation, code queries GitHub releases, downloads a zip, and replaces an installed application bundle.
- On macOS, installation creates and bootstraps a persistent per-user launch agent that runs the package daemon.
- The release updater requires a matching SHA-256 checksum before applying a download.
- The inspected code uses fixed executable paths and argument arrays rather than shell interpolation.
- No runtime dependency on trace-mcp itself or credential-exfiltration path was found.
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.23.2.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.23.2 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.