registry / @togglhq/cli / 1.13.58
@togglhq/cli@1.13.58
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection shows no install hook or concrete attack behavior. The scanner’s credential and network signals correspond to Toggl authentication and workspace API requests using configured service URLs.
Static reason
One or more suspicious static signals were detected.
Trigger
The user runs the CLI authentication flow or requests cached workspace information.
Impact
The inspected behavior supports the CLI’s account and workspace functions; it does not establish unauthorized credential transfer or command-output exfiltration.
Mechanism
The CLI sends a bearer token to the Accounts API URL selected from explicit options or environment settings, defaulting to Toggl’s Accounts service.
AI rationale
Source inspection shows no install hook or concrete attack behavior. The scanner’s credential and network signals correspond to Toggl authentication and workspace API requests using configured service URLs.
Network endpoints2
accounts.toggl.comfocus.toggl.com
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a CLI and program modules, and its manifest declares no install lifecycle hook.
- The authentication flow uses Toggl Accounts and Focus URLs by default; URL overrides come from supplied options or environment configuration, and the authenticated token is sent to the selected Accounts URL for a workspace lookup.
- The CLI loads the active profile and uses its Accounts URL when refreshing cached workspace information; the auth command uses explicit workspace/profile options or prompts in an interactive human session.
- The inspected dependency manifests and entrypoints are consistent with an SDK and CLI; their scripts show no install hook that would alter this package’s install behavior.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedbuild/program-Nzh9v81h.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-Nzh9v81h.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-Nzh9v81h.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-Nzh9v81h.js
HighShellbuild/program-Nzh9v81h.js
HighCredential Redirect Persistencebuild/program-Nzh9v81h.js
HighCommand Output Exfiltrationbuild/program-Nzh9v81h.js
HighTrigger Reachable Command Output Exfiltrationbuild/program-Nzh9v81h.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.58.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.58 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.