registry / @togglhq/cli / 1.13.86
@togglhq/cli@1.13.86
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe suspicious command-output finding is not supported by the inspected analytics path: captured properties omit command arguments and results. The manifest has no install hook, and the inspected authentication path sends the API token to its configured Toggl API endpoint.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI or invoking its authentication flow.
Impact
The inspected behavior supports normal CLI authentication and limited product analytics; no concrete malicious effect was established.
Mechanism
Authentication requests use the configured Toggl API endpoint, which defaults to Toggl Accounts. Analytics properties include tool name and action outcome, while the source excludes command arguments and results.
AI rationale
The suspicious command-output finding is not supported by the inspected analytics path: captured properties omit command arguments and results. The manifest has no install hook, and the inspected authentication path sends the API token to its configured Toggl API endpoint.
Network endpoints1
accounts.toggl.com
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI and library entrypoints, with no install lifecycle hook; the CLI entrypoint initializes product telemetry when run.
- The authentication helper reads a Toggl API token from the environment and sends it through the configured Toggl API request path; the CLI auth flow defaults to Toggl Accounts.
- Product analytics sends an allowlisted tool name and action outcome, with no command arguments or results in the captured properties.
- The inspected Sentry and skills dependency manifests and entry files show ordinary library and CLI package structure; the flagged dependency files expose instrumentation modules and terminal input/output handling.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedbuild/program-YV9YM_Ju.jsView file
6import { fileURLToPath } from "node:url";
L7: import { exec, spawn } from "node:child_process";
L8: import process$1 from "node:process";
High
Child Process
Package source references child process execution.
build/program-YV9YM_Ju.jsView on unpkg · L61830if (process$3.versions?.electron) parseOptions.from = "electron";
L1831: const execArgv = process$3.execArgv ?? [];
L1832: if (execArgv.includes("-e") || execArgv.includes("--eval") || execArgv.includes("-p") || execArgv.includes("--print")) parseOptions.from = "eval";
High
•Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration.
build/program-YV9YM_Ju.js:
import * as readline from "node:readline";
import { mkdir, readFile, stat, writeFile } from "node:fs/promises";
import { createInterface } from "node:readline/promises";
function readline$1() {
const cleanFn = cb(readline$1());
* Returns the width of the active readline, or 80 as default value.
function readlineWidth() {
output: readline$1().output
Findings
5 High2 Medium5 Low
HighChild Processbuild/program-YV9YM_Ju.js
HighShellbuild/program-YV9YM_Ju.js
HighCredential Redirect Persistencebuild/program-YV9YM_Ju.js
HighCommand Output Exfiltrationbuild/program-YV9YM_Ju.js
HighTrigger Reachable Command Output Exfiltrationbuild/program-YV9YM_Ju.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @togglhq/cli@1.13.86.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.86 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.