@vibes.diy/api-svc@14.3.225
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 5d ago · by lpm-firewall-aiThe flagged avatar flow is an explicitly invoked maintenance backfill with a dry-run default and an explicit --apply write gate. The credential and network flows reviewed serve configured embedding and reporting functions; no package-controlled unrelated receiver or automatic exfiltration was found.
Decision evidence
public snapshot- Avatar and embedding backfills are exposed as explicit admin commands in package scripts.
- The avatar backfill defaults to the package’s asset host and performs no writes without --apply.
- The embedding backfill requires --apply and reads its backend URL and API key from configuration; the embedding request sends text and that key to the configured backend URL.
- The alarm code uses separately named PostHog and GitHub credentials for its reporting workflow.
- No install lifecycle scripts are declared.
- The reviewed backfill paths require an explicit command, and write operations require --apply.
- The embedding module sends input only to the supplied backend URL; no hard-coded unrelated receiver was identified.
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 backfill defaults to the package’s asset host and performs no writes without --apply.
usage-report/backfill-avatars.jsView on unpkg · L133Findings
Affected versions and remediation
This report applies to @vibes.diy/api-svc@14.3.225.
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.225 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.