registry / @togglhq/cli / 1.13.79
@togglhq/cli@1.13.79
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or malicious credential-transfer path; the scanner’s command and network signals correspond to CLI functionality and limited first-party analytics. The flagged dependency excerpts show prompt and telemetry instrumentation, not package attack behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the Toggl CLI or invokes one of its commands.
Impact
No confirmed credential theft, command-output exfiltration, install-time mutation, or other attack behavior was established.
Mechanism
The CLI handles Toggl authentication and API requests. Product analytics sends an allowlisted command event to the configured PostHog collector.
AI rationale
Source inspection found no lifecycle hook or malicious credential-transfer path; the scanner’s command and network signals correspond to CLI functionality and limited first-party analytics. The flagged dependency excerpts show prompt and telemetry instrumentation, not package attack behavior.
Evidence
package.jsonbuild/cli.jsbuild/program-DWpgFJoy.js
Network endpoints1
eu.i.posthog.com
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a Toggl CLI and has no install lifecycle hook; its CLI entrypoint initializes telemetry and parses user commands.
- The flagged bundle’s API key handling describes sending the caller’s Toggl API key to Toggl’s API; OAuth clients use first-party Toggl accounts endpoints.
- Analytics sends an allowlisted command name, action, outcome, client, session identifier, and package version to the configured PostHog collector; it does not include command arguments or results.
- The inspected dependency entrypoints and flagged dependency paths contain CLI prompt code and Sentry/OpenTelemetry instrumentation; no attack behavior was identified in those excerpts.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedbuild/program-DWpgFJoy.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-DWpgFJoy.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-DWpgFJoy.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-DWpgFJoy.js
HighShellbuild/program-DWpgFJoy.js
HighCredential Redirect Persistencebuild/program-DWpgFJoy.js
HighCommand Output Exfiltrationbuild/program-DWpgFJoy.js
HighTrigger Reachable Command Output Exfiltrationbuild/program-DWpgFJoy.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.79.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.79 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.