@vibes.diy/api-svc@14.3.166
⚠ 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 15d ago · by lpm-firewall-aiThe scanner's avatar exfiltration claim is not supported by the inspected flow, which is an explicit migration with a dry-run default and an apply gate. Unresolved selected dependency source prevents a complete source review, so this requires manual review rather than a malicious verdict.
Decision evidence
public snapshot- The manifest lists the flagged avatar utility as an admin command and declares runtime dependencies, including @adviser/cement.
- The utility uses a dry run by default; writes require --apply and a database admin URL.
- The utility fetches avatar images and, on apply, stores transformed images in its configured R2 bucket.
- The utility loads local development variables, and the package entrypoint exports library modules.
- The inspected avatar flow does not establish the scanner's claimed credential or application-record exfiltration: it processes avatar images for a migration and has an explicit write gate.
- The available source snapshot leaves selected runtime dependencies unresolved, so the package cannot be fully cleared from the inspected files.
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.166.
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.166 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.