registry / @togglhq/cli / 1.13.122
@togglhq/cli@1.13.122
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged command and network behavior corresponds to documented CLI telemetry and error reporting. Analytics is limited to command metadata with an opt-out, and the error flow is redacted and documented; no credential exfiltration or command-output collection was found.
Static reason
One or more suspicious static signals were detected.
Trigger
Runtime CLI invocation; analytics records a command after it runs, and error reporting handles CLI exceptions.
Impact
The reviewed flows do not send command arguments or output, and the error reporting scrubber removes sensitive request and host fields.
Mechanism
Product analytics sends allowlisted command metadata to eu.i.posthog.com. Redacted error reports go to o43910.ingest.us.sentry.io; both have documented opt-outs.
AI rationale
The flagged command and network behavior corresponds to documented CLI telemetry and error reporting. Analytics is limited to command metadata with an opt-out, and the error flow is redacted and documented; no credential exfiltration or command-output collection was found.
Network endpoints2
eu.i.posthog.como43910.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts; it exposes a CLI and an import entry that exports createProgram.
- The README discloses product analytics fields, says command arguments and output are not collected, and documents TOGGL_PRODUCT_ANALYTICS=off.
- The analytics implementation sends a strict allowlist of tool name, action, outcome, client, session ID, and package version; it does not accept arguments or results.
- The README describes the default error reporting fields and its TOGGL_SENTRY=off option; the Sentry scrubber removes hostname, request data, and API keys.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 flaggedbuild/program-SViaV6up.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-SViaV6up.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-SViaV6up.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-SViaV6up.js
HighShellbuild/program-SViaV6up.js
HighCredential Redirect Persistencebuild/program-SViaV6up.js
HighCommand Output Exfiltrationbuild/program-SViaV6up.js
HighTrigger Reachable Command Output Exfiltrationbuild/program-SViaV6up.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.122.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.122 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.