@catchmexz/fedin-vibe-mcp-server-workbuddy@1.5.0
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged network flow is tied to an explicit deployment request and serves the tool’s stated purpose. However, the archive exclusions leave ordinary `.env` files eligible for upload, creating a real risk that project secrets are sent to the deployment service.
Decision evidence
public snapshot- The deploy tool is documented for use when the user needs to deploy and requires a project path.
- The deployment archive excludes `.env.local` and `.env.*.local`, but not other `.env` files.
- The tool sends the project archive and deploy token to `https://ai.fedin.cn/api/edgeone-pages/deploy`.
- The upload runs through an explicitly invoked deploy tool, rather than automatically on install, import, or startup.
- The endpoint is the package’s deployment service, and uploading project files is the tool’s stated purpose.
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.5.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.5.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.