trace-mcp@3.37.2
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 9d ago · by lpm-firewall-aiThe high-similarity scanner hits point to ordinary maintenance, benchmark, documentation, and performance scripts. The automatic setup is scoped to trace-mcp, and the inspected agent-configuration matches are path declarations rather than configuration mutations.
Decision evidence
public snapshot- package.json runs a native preflight and package-owned app and control-plane setup from postinstall.
- The agent-integration hits in dist/extract-worker.js and dist/proxy.js declare paths for agent directories; the inspected matches do not show configuration writes.
- The named scripts implement benchmarks, session-log analysis, screenshot and fixture capture, update checks, and documentation or performance utilities.
- The control-plane hook skips ephemeral installs and respects the daemon opt-out; app updates require a matching checksum.
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.2.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.37.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.