buildpartner@0.15.0
Your AI build partner. Expert guidance inside Claude Code.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected code uses the saved BuildPartner token for requests to the service’s default or user-configured API base. BuildPad uploads only a path supplied to its tool and filters hidden paths and credential-like files; the package declares no install lifecycle hook.
Decision evidence
public snapshot- The package exposes a CLI; its scripts are build and dev, with no install lifecycle hook.
- The API client defaults to BuildPartner’s HTTPS host and sends its saved token as a bearer credential to the configured API base.
- BuildPad uploads a path supplied to its explicit create action to the BuildPartner pads API.
- Folder uploads skip hidden paths and exclude credential-like filenames and files with .env, .pem, or .key extensions.
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 package exposes a CLI; its scripts are build and dev, with no install lifecycle hook.
package.jsonView on unpkg · L16Findings
Affected versions and remediation
This report applies to buildpartner@0.15.0.
See all versions of buildpartner for other recorded verdicts.
- Review the evidence and your use of buildpartner@0.15.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.