registry / @withone/cli / 2.6.0
@withone/cli@2.6.0
CLI for managing One
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe package’s `prepare` hook runs `tsup`, while agent skill installation and credential setup are part of the explicit `init` flow. The inspected code does not substantiate the scanner’s claims of an automatic credential redirect or install-time agent control-surface mutation.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes `one init` or chooses custom API configuration.
Impact
No confirmed malicious impact or attack surface was established.
Mechanism
The CLI validates credentials against the selected endpoint and installs its own skill during setup; no inspected source shows a package-install-triggered agent configuration write.
AI rationale
The package’s `prepare` hook runs `tsup`, while agent skill installation and credential setup are part of the explicit `init` flow. The inspected code does not substantiate the scanner’s claims of an automatic credential redirect or install-time agent control-surface mutation.
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 runs `tsup` for `prepare`; it has no automatic install hook.
- The CLI’s `init` command sets up One and installs its agent skill; credential validation and skill installation occur in that setup flow.
- Agent configuration paths are used by configuration helper code; inspected source does not establish an install-time write to those files.
- The child-process import in the memory bundle is part of embedded PostgreSQL daemon support.
Evidence against
- The scanner flags credential redirection and agent control-surface mutation, but inspected excerpts show a user-selected custom API endpoint and an explicit setup command, not an automatic attack.
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.6.0.
See all versions of @withone/cli for other recorded verdicts.
- Review the evidence and your use of @withone/cli@2.6.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.