registry / @withone/cli / 2.4.0
@withone/cli@2.4.0
CLI for managing One
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest and inspected runtime paths do not support the scanner’s credential-redirection or persistence claims. The observed API and embedding requests are service-aligned, and the runtime analytics behavior does not establish a concrete attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI or using its exported API; embedding requests additionally require the OpenAI provider and a configured key.
Impact
No confirmed credential theft, persistence attack, or install-time disclosure was established.
Mechanism
The inspected login path sends requests through the configured One API base. Embedding code uses the OpenAI service. Runtime analytics code sends events to its configured PostHog host and includes telemetry disable settings.
AI rationale
The manifest and inspected runtime paths do not support the scanner’s credential-redirection or persistence claims. The observed API and embedding requests are service-aligned, and the runtime analytics behavior does not establish a concrete attack.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and an import entrypoint; its only lifecycle hook is prepare running the build tool.
- The browser-login result is passed to the One API client using the configured API base; the client defaults to api.withone.ai and sends requests to that base.
- OpenAI embeddings require the configured OpenAI provider and key, and use the OpenAI embeddings service.
- The reviewed dependency snapshots show prompt, terminal-color, and command-parsing libraries; the inspected package manifests show no lifecycle scripts.
Evidence against
- Scanner hints alleging a fixed unofficial credential gateway were not corroborated: the inspected login and API client code uses the configured One API base.
- The package does collect and send analytics at runtime, with telemetry disable settings; the inspected source does not show that this is an install-time disclosure or an unrelated credential transfer.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
Source & flagged code
11 flaggeddist/chunk-NOPTG4GC.jsView file
1465import { createRequire } from "module";
L1466: import { spawn, spawnSync } from "child_process";
L1467: var requireFromHere = createRequire(import.meta.url);
High
Child Process
Package source references child process execution.
dist/chunk-NOPTG4GC.jsView on unpkg · L14651773patternName = generic_password
severity = medium
line = 1773
Medium
Secret Pattern
Package contains a possible secret pattern.
dist/chunk-NOPTG4GC.jsView on unpkg · L1773dist/index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @withone/cli@1.53.0
matchedIdentity = npm:QHdpdGhvbmUvY2xp:1.53.0
similarity = 0.625
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
Findings
1 Critical5 High6 Medium9 Low
CriticalPrevious Version Dangerous Deltadist/index.js
HighChild Processdist/chunk-NOPTG4GC.js
HighShelldist/index.js
HighCredential Redirect Persistencedist/index.js
HighCross File Remote Execution Contextdist/index.js
HighTrigger Reachable Persistencedist/index.js
MediumSecret Patterndist/chunk-NOPTG4GC.js
MediumDynamic Requiredist/chunk-XKUTG7JD.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to @withone/cli@2.4.0.
See all versions of @withone/cli for other recorded verdicts.
- Review the evidence and your use of @withone/cli@2.4.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.