registry / @togglhq/cli / 1.13.72
@togglhq/cli@1.13.72
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection resolved the scanner's shell and network matches to browser opening, expected OAuth, and limited Toggl product analytics. The manifest has no install-time lifecycle hook, and the inspected subprocess path is a user-invoked setup command.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI invokes its parser and telemetry setup; authentication and skills setup run through their respective CLI actions.
Impact
No command-output collection, unrelated credential transfer, or harmful package-install mutation was established.
Mechanism
OAuth sends its authorization code to the configured Toggl Accounts service. Analytics sends a limited command event to Toggl's PostHog collector, while the shell call opens the authentication URL in a browser.
AI rationale
Source inspection resolved the scanner's shell and network matches to browser opening, expected OAuth, and limited Toggl product analytics. The manifest has no install-time lifecycle hook, and the inspected subprocess path is a user-invoked setup command.
Network endpoints2
accounts.toggl.comeu.i.posthog.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and lists no install-time lifecycle hook; build/cli.js starts the command parser when invoked.
- OAuth exchanges an authorization code and PKCE verifier with the configured Toggl Accounts service.
- Product analytics can be disabled and sends command, action, outcome, session, and package-version fields to the Toggl PostHog collector.
- The shell call opens the OAuth URL in a browser; the inspected setup subprocess inherits stdio and is run by a CLI command.
- The inspected dependency paths contain Sentry instrumentation exports and interactive prompt imports, not evidence of the flagged credential or command-output attack.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 flaggedbuild/program-Cm5YGViI.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-Cm5YGViI.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-Cm5YGViI.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-Cm5YGViI.js
HighShellbuild/program-Cm5YGViI.js
HighCredential Redirect Persistencebuild/program-Cm5YGViI.js
HighCommand Output Exfiltrationbuild/program-Cm5YGViI.js
HighTrigger Reachable Command Output Exfiltrationbuild/program-Cm5YGViI.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.72.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.72 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.