buildpartner@0.15.4
Your AI build partner. Expert guidance inside Claude Code.
AI Security Review
scanned 23h ago · by lpm-firewall-aiThe package automatically sends limited installation and runtime telemetry to its own service when its MCP server connects. The source describes the report, but no opt-out is apparent in the inspected code, so this warrants a warning; no unrelated credential exfiltration or other attack behavior was identified.
Decision evidence
public snapshot- When the MCP server connects, it reports an install event to the configured BuildPartner API, including a saved install ID, platform, architecture, package version, and Node version.
- The report runs after the server handshake and is sent once per version, with up to three attempts when offline.
- No install lifecycle hook is declared; the CLI dispatches only explicit commands.
- API requests use BuildPartner’s default service host, or a base URL configured by the user.
- The inspected report contains runtime and install identifiers, not environment values, credentials from other services, or file contents.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/src/mcp/build-pad.jsView on unpkg · L20This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/src/commands/setup.jsView on unpkgFindings
Affected versions and remediation
This report applies to buildpartner@0.15.4.
See all versions of buildpartner for other recorded verdicts.
- Review the evidence and your use of buildpartner@0.15.4 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.