buildpartner@0.15.2
Your AI build partner. Expert guidance inside Claude Code.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package otherwise uses its saved token to authenticate with its own BuildPartner API, but its 403 response directs an AI agent to expose that token in a URL query string. This conditional credential-handling risk warrants a warning.
Decision evidence
public snapshot- When an expert-knowledge API call returns HTTP 403, the MCP tool returns an action instructing the agent to read the local auth file and put its token in a dashboard URL query parameter.
- The API client reads the token from local auth and sends it to the configured BuildPartner API base; the default is https://www.buildpartner.ai.
- The package has no install lifecycle scripts; its CLI starts the MCP server only when the user runs the serve command.
- The token-in-URL instruction is limited to the API's 403 subscription response and directs the user to the BuildPartner dashboard.
Source & flagged code
4 flaggedWhen an expert-knowledge API call returns HTTP 403, the MCP tool returns an action instructing the agent to read the local auth file and put its token in a dashboard URL query parameter.
dist/src/mcp/server.jsView on unpkg · L184When an expert-knowledge API call returns HTTP 403, the MCP tool returns an action instructing the agent to read the local auth file and put its token in a dashboard URL query parameter.
dist/src/mcp/server.jsView on unpkg · L77Findings
Affected versions and remediation
This report applies to buildpartner@0.15.2.
See all versions of buildpartner for other recorded verdicts.
- Review the evidence and your use of buildpartner@0.15.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.