registry / @vibes.diy/api-svc / 14.3.211
@vibes.diy/api-svc@14.3.211
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 database, asset, embedding, and reporting operations are exposed as administrative commands, with writes gated by explicit flags and service credentials directed to their configured services. I found no install-time or import-time malicious behavior in the reviewed paths.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
No install-time or import-time attack identified; administrative writes require an explicit command and flags.
Impact
No malicious impact identified in the inspected source.
Mechanism
Backfills process package data and use configured service endpoints; the inspected alarm code sends GitHub credentials to api.github.com when --write is selected.
AI rationale
The flagged database, asset, embedding, and reporting operations are exposed as administrative commands, with writes gated by explicit flags and service credentials directed to their configured services. I found no install-time or import-time malicious behavior in the reviewed paths.
Network endpoints4
vibes.diy (overridable via ASSET_FETCH_BASE)us.posthog.com (overridable via POSTHOG_HOST)api.github.comLLM_BACKEND_URL (operator-configured)
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies index.js as the main entry and declares no install lifecycle hook.
- The avatar backfill defaults to a dry run; writes require the explicit --apply flag.
- The embedding backfill requires an operator-configured LLM_BACKEND_URL and LLM_BACKEND_API_KEY for --apply, then sends app text to that configured endpoint for embeddings.
- The alarm scripts use POSTHOG_API_KEY with PostHog and use GITHUB_TOKEN with the GitHub API only when --write is selected.
- The main entry re-exports the embedding feature; the inspected code shows no import-time invocation of the backfill scripts.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedusage-report/backfill-avatars.jsView file
1import { spawnSync } from "node:child_process";
L2: import * as fs from "node:fs";
...
L24: NEON_DATABASE_ADMIN_URL write connection (required for --apply)
L25: ASSET_FETCH_BASE public host serving /assets/cid/ (default https://vibes.diy)
L26: --apply additionally shells out to \`wrangler r2 object put\` — wrangler must be
...
L37: throw new Error(`fetch ${row.getURL} returned ${res.status}`);
L38: const buf = Buffer.from(await res.arrayBuffer());
L39: if (buf.byteLength !== row.size) {
...
L92: return Result.Err(`wrangler r2 object get exited ${res.status}`);
L93: if (res.stdout.equals(work.newBytes) === false)
L94: return Result.Err("stored avatar differs from transformed bytes");
...
L140: const apply = args.includes("--apply");
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
usage-report/backfill-avatars.jsView on unpkg · L1usage-report/r2-affected-apps.shView file
•path = usage-report/r2-affected-apps.sh
kind = build_helper
sizeBytes = 2493
magicHex = [redacted]
Medium
Ships Build Helper
Findings
1 Critical2 High4 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationusage-report/backfill-avatars.js
HighSemantic Analysis Limitedintern/design-repair.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltaintern/opens-check.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperusage-report/r2-affected-apps.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @vibes.diy/api-svc@14.3.211.
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.211 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.