@togglhq/cli@1.13.141
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe source shows default runtime Sentry reporting to a fixed endpoint, while the README describes product analytics without mentioning Sentry. The events are scrubbed and the behavior is limited to CLI execution errors, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the CLI and a command throws an error.
Impact
Limited diagnostic telemetry leaves the machine without documented consent. Source scrubbing reduces the data sent.
Mechanism
The CLI sends a scrubbed exception event to the built-in Sentry endpoint; reporting can be disabled through environment settings, but the README does not disclose it.
AI rationale
The source shows default runtime Sentry reporting to a fixed endpoint, while the README describes product analytics without mentioning Sentry. The events are scrubbed and the behavior is limited to CLI execution errors, so this warrants a warning rather than a block.
Evidence
build/cli.jsbuild/program-BYXXg7fB.jsREADME.md
Network endpoints2
o43910.ingest.us.sentry.ioeu.i.posthog.com
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI initializes Sentry with a built-in endpoint when its entry point runs.
- When enabled, Sentry reports CLI exceptions during command execution.
- The README documents product analytics and its opt-out, but does not mention Sentry error reporting.
- Sentry events are scrubbed to remove hostnames, breadcrumbs, request data, and unsafe error messages.
Evidence against
- Product analytics is documented, can be disabled with TOGGL_PRODUCT_ANALYTICS=off, and excludes command arguments and output.
- The analytics event code uses a limited set of fields and does not accept command arguments or results.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 flaggedbuild/program-BYXXg7fB.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-BYXXg7fB.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-BYXXg7fB.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-BYXXg7fB.js
HighShellbuild/program-BYXXg7fB.js
HighCredential Redirect Persistencebuild/program-BYXXg7fB.js
HighCommand Output Exfiltrationbuild/program-BYXXg7fB.js
HighTrigger Reachable Command Output Exfiltrationbuild/program-BYXXg7fB.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.141.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.141 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.