@vibes.diy/api-svc@14.3.193
⚠ Under reviewWebSocket-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 10d ago · by lpm-firewall-aiThe avatar alert resolves to an explicitly applied migration, and embedding requests use the supplied backend URL and key. I cannot clear the package because the runtime lint dependency imported by design repair was unavailable for source inspection.
Decision evidence
public snapshot- The avatar migration requires an explicit `--apply` flag; without it, the script reports a dry run and returns.
- The embedding helper sends app text and a supplied key to the backend URL passed by its caller.
- Design repair imports and invokes `@vibes.diy/pouf/lint`, but that dependency’s source was unavailable in the package snapshot.
- The inspected avatar migration writes transformed images to the package’s configured R2 bucket and updates matching avatar records; it does not establish an unrelated data receiver.
- The inspected embedding code is consistent with sending text to a caller-supplied model backend, not a package-selected recipient.
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 · L1The avatar migration requires an explicit `--apply` flag; without it, the script reports a dry run and returns.
usage-report/backfill-avatars.jsView on unpkg · L140Findings
Affected versions and remediation
This report applies to @vibes.diy/api-svc@14.3.193.
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.193 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.