@vibes.diy/api-svc@14.3.246
WebSocket-based API for vibes.diy chat persistence and app deployment. Supports both HTTP POST and WebSocket connections using the same handler via the Evento event-driven framework.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe scanner’s avatar finding is an operator-run backfill with dry-run behavior and an explicit --apply gate. The PostHog and GitHub flows are reporting commands whose writes require --write, while embedding requests use a caller-configured backend and key; no malicious default behavior was found in the reviewed paths.
Decision evidence
public snapshot- The manifest points to index.js and declares named build, reporting, and admin commands; it has no install lifecycle hook.
- The avatar backfill defaults to a dry run and selects the admin database URL only when --apply is supplied.
- The alarm command reads a PostHog key and supports issue writes only with an explicit --write flag and GitHub credentials.
- Embedding requests go to a caller-supplied backend URL and use its supplied API key.
- The flagged avatar backfill fetches and transforms stored avatars, then writes them to the service’s R2 bucket and database when explicitly applied.
- The reporting commands query PostHog and can create or update issues in the repository selected by the operator.
- The embedding code sends text to its configured embedding backend as part of the service’s application functionality.
Source & flagged code
5 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
usage-report/backfill-avatars.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @vibes.diy/api-svc@14.3.246.
See all versions of @vibes.diy/api-svc for other recorded verdicts.
- Review the evidence and your use of @vibes.diy/api-svc@14.3.246 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.