post-engineer-mcp@1.30.0
Post Engineer MCP Server for AI pair programming and agentic workflows
AI Security Review
scanned 26d ago · by lpm-firewall-aiSource inspection found no malicious behavior: the only lifecycle script is prepublishOnly build, and analytics is gated by an explicitly configured key. Tracked properties in the inspected active path are tool names, while the API client's URL and credential come from caller configuration.
Decision evidence
public snapshot- package.json runs only a build during prepublishOnly; it defines no install lifecycle hook.
- Analytics sends tool-call event properties only when POSTHOG_API_KEY is configured, and scrubs secret-like property keys.
- The active server wraps tool handlers with tracking; inspected code tracks tool names rather than request bodies or credentials.
- The API client takes its URL and API key from caller configuration.
Source & flagged code
2 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/analytics.jsView on unpkg · L61package.json runs only a build during prepublishOnly; it defines no install lifecycle hook.
package.jsonView on unpkg · L22Findings
Affected versions and remediation
This report applies to post-engineer-mcp@1.30.0.
See all versions of post-engineer-mcp for other recorded verdicts.
- Review the evidence and your use of post-engineer-mcp@1.30.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.