@vibes.diy/api-svc@14.3.219
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 6d ago · by lpm-firewall-aiThe flagged avatar path is an explicit admin backfill that defaults to a dry run, and its writes target the project’s R2 storage and database. Embedding uses a configured backend and is gated in the backfill command by --apply; no install-time or import-time attack behavior was found.
Decision evidence
public snapshot- The manifest’s main entry is index.js; its listed operational tools are named npm scripts, including explicit admin backfills.
- The avatar backfill uses --apply to select the admin database connection; without it, the script is a dry run.
- The embedding backfill requires --apply before it needs LLM_BACKEND_URL and LLM_BACKEND_API_KEY; the key is sent to the configured embedding backend.
- The embedding code sends text to the supplied backend URL, rather than choosing a hard-coded foreign receiver.
- The alarm tooling uses separate PostHog and GitHub credentials for their corresponding services.
- The package contains network, filesystem, and process-execution code for its administrative backfill tools.
- The embedding feature transmits app or chat-derived text and a bearer key to the configured backend when invoked.
- Alarm scripts can query PostHog and create or update GitHub issues when run with --write.
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.219.
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.219 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.