buildpartner@0.15.3
Your AI build partner. Expert guidance inside Claude Code.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package has no install-time hooks, and its CLI runs selected commands only when invoked. Credential use is directed to the configured BuildPartner API, while BuildPad publication is user-triggered and excludes neighboring data files by default.
Decision evidence
public snapshot- The manifest has no install or lifecycle hooks; its scripts are build and dev commands.
- The CLI dispatches only when a command is supplied, to serve, doctor, or login.
- API requests use the saved token with the configured BuildPartner API base; the base comes from BP_API_BASE, saved auth configuration, or the BuildPartner production URL.
- BuildPad exposes publishing through an MCP tool call, and says data files stay local unless include_data is passed.
Source & flagged code
4 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/src/mcp/build-pad.jsView on unpkgThe manifest has no install or lifecycle hooks; its scripts are build and dev commands.
package.jsonView on unpkg · L1Findings
Affected versions and remediation
This report applies to buildpartner@0.15.3.
See all versions of buildpartner for other recorded verdicts.
- Review the evidence and your use of buildpartner@0.15.3 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.