trace-mcp@3.17.1
Framework-aware code intelligence MCP server — 87 framework integrations, 81 languages, 40–50% fewer tokens on average
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has a concrete automatic persistence and self-update lifecycle, which is risky for an npm package. Its actions appear scoped to trace-mcp-owned resources and include update verification, so the source does not establish malicious intent or broader compromise.
Decision evidence
public snapshot- The package runs three scripts automatically after installation.
- The install hook creates a user launch agent that keeps a trace-mcp daemon running and starts it at load.
- On macOS, installation can download a release archive and replace an installed trace-mcp application bundle.
- The persistence is explicitly scoped to trace-mcp paths and its own launch-agent label.
- The app updater requires a matching SHA-256 checksum before applying an update.
- The hook provides opt-out environment variables and skips development checkouts.
Source & flagged code
15 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/verify-upgrade-path.mjsView on unpkg · L25Findings
Affected versions and remediation
This report applies to trace-mcp@3.17.1.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.17.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.