registry / @withone/cli / 2.7.0
@withone/cli@2.7.0
CLI for managing One
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest’s `prepare` hook only runs the build tool. Inspected runtime behavior supports user-configured API access and CLI-driven first-party skill setup; the scanner signals do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the CLI initialization or configures a custom API endpoint.
Impact
No confirmed unauthorized credential transfer or agent control-surface abuse was established.
Mechanism
The CLI prompts for a custom endpoint and validates the supplied key against it; initialization installs package-owned skills for supported agents.
AI rationale
The manifest’s `prepare` hook only runs the build tool. Inspected runtime behavior supports user-configured API access and CLI-driven first-party skill setup; the scanner signals do not establish malicious behavior.
Network endpoints2
api.withone.aidevelopment-api.withone.ai
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines `prepare` as `tsup`; no install lifecycle hook was found.
- Custom API configuration prompts for an endpoint, then validates the entered key against that endpoint.
- The CLI’s skill installation is called from initialization and copies package-owned skills into agent skill directories.
- The inspected agent definitions identify supported configuration locations; this excerpt does not establish an unconsented configuration write.
- The memory bundle imports memory helpers and an OpenAI key accessor; the inspected source does not establish credential exfiltration.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
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 · L17731310if (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-NOPTG4GC.jsView on unpkg · L1310dist/index.js
Findings
6 High6 Medium9 Low
HighChild Processdist/chunk-NOPTG4GC.js
HighShelldist/index.js
HighCredential Redirect Persistencedist/index.js
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/index.js
HighCross File Remote Execution Contextdist/index.js
HighTrigger Reachable Persistencedist/index.js
MediumSecret Patterndist/chunk-NOPTG4GC.js
MediumDynamic Requiredist/chunk-NOPTG4GC.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.7.0.
See all versions of @withone/cli for other recorded verdicts.
- Review the evidence and your use of @withone/cli@2.7.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.