trace-mcp@3.37.9
Framework-aware code intelligence MCP server — 88 framework integrations, 81 languages, 72.7% fewer input tokens to review a pull request, comprehension at parity
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe scanner’s similarity and agent-configuration hints do not establish malicious behavior in the inspected source. The postinstall work is package-aligned launcher and daemon setup, and the flagged scripts are development or documentation utilities.
Decision evidence
public snapshot- package.json exposes the package CLI and runs native preflight, app update, and control-plane setup during postinstall.
- The agent-configuration matches are home-directory path constants, benchmark input, or a session-log read; the inspected excerpts do not show agent configuration mutation.
- The flagged scripts identify documentation generation, benchmarks, fixtures, and upgrade checks.
- The control-plane postinstall can be disabled and skips development checkouts; it writes launcher settings and a shim for this package’s own CLI, with a daemon opt-out.
- The app updater targets legacy trace-mcp app bundles, while the native preflight only asks macOS to verify bundled native modules.
Source & flagged code
26 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.37.9.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.37.9 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.