@catchmexz/fedin-vibe-mcp-server-workbuddy@1.7.0
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package’s deploy tool uploads the caller-selected project to its own deployment service, which fits its stated purpose. However, its archive excludes local env variants but not `.env`, so a user-requested deployment can forward secrets stored there; this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- The deploy tool is described for use when the user needs to deploy, and accepts a project path.
- The deploy handler passes that supplied path and the Fedin deploy token to the deploy operation.
- The archive excludes `.env.local` and `.env.*.local`, but does not exclude a plain `.env` file.
- Files not excluded are added to the project archive, which is uploaded to `ai.fedin.cn` with the deploy token.
- The project upload happens through the explicit deploy tool flow, matching the package’s stated deployment purpose.
- The upload endpoint is the package’s Fedin deployment service, and the token is sent to that service.
- The archive excludes several common local and generated directories, including `node_modules`, `.git`, and `.env.local`.
Source & flagged code
4 flaggedSource appears to send environment or credential material to an external endpoint.
dist/operations/deploy/deploy.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to @catchmexz/fedin-vibe-mcp-server-workbuddy@1.7.0.
See all versions of @catchmexz/fedin-vibe-mcp-server-workbuddy for other recorded verdicts.
- Review the evidence and your use of @catchmexz/fedin-vibe-mcp-server-workbuddy@1.7.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.