registry / @withone/cli / 1.57.0
@withone/cli@1.57.0
CLI for managing One
AI Security Review
scanned 12d ago · by lpm-firewall-aiInspected source shows prompted API-key validation against the selected service and ordinary command telemetry with opt-outs. The scanner’s credential-redirection and persistence claims were not established by the source reviewed.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running a CLI command can record and send usage events; authentication setup validates a key after the user supplies it.
Impact
The inspected credential paths do not show keys being sent to the telemetry collector or an unrelated fixed gateway.
Mechanism
The telemetry code posts event data to the configured PostHog host. API key validation uses the API base selected by the user or the documented default service.
AI rationale
Inspected source shows prompted API-key validation against the selected service and ordinary command telemetry with opt-outs. The scanner’s credential-redirection and persistence claims were not established by the source reviewed.
Network endpoints2
us.i.posthog.comapi.withone.ai
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 exposes the CLI through bin/cli.js, which imports dist/index.js; its prepare hook runs the build tool.
- When choosing a custom API base, the CLI prompts for that URL and validates the entered key against it. When restoring the default, it prompts for a key for api.withone.ai and validates it there.
- The bundle’s telemetry code sends usage events to the PostHog host and provides environment and configuration opt-outs; no inspected source showed API credentials being sent to that collector.
- The inspected dependency entrypoints are prompt, color-formatting, and CLI parsing libraries; no attack behavior was identified in the required dependency paths.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
Source & flagged code
10 flaggeddist/chunk-VH46MAE4.jsView file
1462import { createRequire } from "module";
L1463: import { spawn } from "child_process";
L1464: var requireFromHere = createRequire(import.meta.url);
High
Child Process
Package source references child process execution.
dist/chunk-VH46MAE4.jsView on unpkg · L14621310if (this.backend) return this.backend;
L1311: const pg = await import("pg").catch((err) => {
L1312: const msg = err instanceof Error ? err.message : String(err);
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-VH46MAE4.jsView on unpkg · L1310dist/index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @withone/cli@1.53.0
matchedIdentity = npm:QHdpdGhvbmUvY2xp:1.53.0
similarity = 0.750
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Findings
1 Critical5 High5 Medium9 Low
CriticalPrevious Version Dangerous Deltadist/index.js
HighChild Processdist/chunk-VH46MAE4.js
HighShelldist/index.js
HighCredential Redirect Persistencedist/index.js
HighCross File Remote Execution Contextdist/index.js
HighTrigger Reachable Persistencedist/index.js
MediumDynamic Requiredist/chunk-VH46MAE4.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEval
Affected versions and remediation
This report applies to @withone/cli@1.57.0.
See all versions of @withone/cli for other recorded verdicts.
- Review the evidence and your use of @withone/cli@1.57.0 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.