registry / @vibes.diy/api-svc / 14.3.138
@vibes.diy/api-svc@14.3.138
⚠ 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 19d ago · by lpm-firewall-aiThe flagged source is an explicitly invoked maintenance command with a dry-run default and an explicit write flag. The required clean citation coverage exceeds the 128-citation limit, so the package needs manual review rather than a clean verdict.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The script runs when explicitly invoked as an administrative command.
Impact
The inspected behavior is consistent with an administrative avatar backfill; broader package behavior remains unresolved.
Mechanism
It reads avatar records, fetches image data from the configured service host, and requires --apply to perform writes.
AI rationale
The flagged source is an explicitly invoked maintenance command with a dry-run default and an explicit write flag. The required clean citation coverage exceeds the 128-citation limit, so the package needs manual review rather than a clean verdict.
Evidence
package.jsonusage-report/backfill-avatars.js
Network endpoints1
vibes.diy
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json registers the flagged file as an explicit admin command, with no install lifecycle hook.
- The avatar script defaults to vibes.diy and requires --apply for its write pass.
- The script describes its default run as a dry run.
Evidence against
- The required clean review covers more paths than the 128 citation limit allows.
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.138.
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.138 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.