post-engineer-mcp@1.33.0
Post Engineer MCP Server for AI pair programming and agentic workflows
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s runtime telemetry is documented and disabled unless POSTHOG_API_KEY is configured; the tracked event contains only the tool name. The default HTTP listener is stdio, and the inspected API credential flow targets the configured service API.
Decision evidence
public snapshot- The manifest points the executable to dist/index.js; its prepublishOnly hook only builds the package.
- README documents optional PostHog telemetry and says it is disabled without POSTHOG_API_KEY.
- Analytics reads POSTHOG_API_KEY and returns without initializing PostHog when it is absent.
- Tracked events contain the tool name and use a fixed package distinct ID; the wrapper does not pass tool arguments.
- The server starts HTTP transport only when explicitly given --http-transport; otherwise it uses stdio.
- The API client sends its configured API key to the configured Post Engineer API base URL.
Source & flagged code
2 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/analytics.jsView on unpkg · L61The manifest points the executable to dist/index.js; its prepublishOnly hook only builds the package.
package.jsonView on unpkg · L18Findings
Affected versions and remediation
This report applies to post-engineer-mcp@1.33.0.
See all versions of post-engineer-mcp for other recorded verdicts.
- Review the evidence and your use of post-engineer-mcp@1.33.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.