@vibes.diy/api-svc@14.3.254
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 2d ago · by lpm-firewall-aiThe flagged data flows serve the package’s avatar maintenance, reporting, and embedding features. The backfill and GitHub issue writes have explicit command-line gates, and the credential-bearing requests use their configured service endpoints.
Decision evidence
public snapshot- The manifest has no lifecycle scripts; its main entry is index.js and maintenance jobs are separate npm scripts.
- The avatar backfill defaults to a dry run and says it writes only with --apply.
- The backfill fetches avatar assets from the configured asset host and processes them for storage in the package’s R2 bucket.
- Embedding requests send feature text to the supplied backend URL with that backend’s API key.
- The alarm tools use a configurable PostHog host and require --write plus a configured GitHub repository and token before issue writes.
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 a dry run and says it writes only with --apply.
usage-report/backfill-avatars.jsView on unpkg · L143Findings
Affected versions and remediation
This report applies to @vibes.diy/api-svc@14.3.254.
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.254 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.