@vibes.diy/api-svc@14.3.230
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 data flows are purpose-aligned operations: avatar migration is read-only by default, alarm issue writes require `--write`, and embedding credentials go to the configured backend. No install-time or import-time attack behavior was found in the reviewed paths.
Decision evidence
public snapshot- The manifest exposes the flagged backfill and alarm tools as explicit scripts; it declares no install lifecycle hook.
- The avatar backfill defaults to a dry run and only writes when invoked with `--apply`.
- The backfill stores transformed avatars in its declared R2 bucket through Wrangler, consistent with its migration purpose.
- The alarm reads PostHog settings from environment variables and defaults to PostHog; GitHub access uses the configured repository and is gated by `--write`.
- Embedding requests use the backend URL and API key supplied through dependencies, rather than a hard-coded foreign receiver.
- When explicitly applied, the avatar backfill reads user avatar records and writes transformed assets and updated database rows.
- When explicitly run with `--write`, alarm scripts can publish summaries as GitHub issues.
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.230.
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.230 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.