@togglhq/cli@1.13.95
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe scanner’s command-output and credential-redirection signals were not supported by the inspected data flow: child processes inherit stdio, while analytics sends allowlisted command metadata to Toggl’s configured collector. The required entrypoint and dependency paths were inspected, and no concrete attack behavior was found.
Decision evidence
public snapshot- package.json exposes the CLI and library entrypoints and has no install lifecycle hook.
- The CLI starts telemetry, while the analytics collector accepts a strict set of command metadata and excludes arguments and results.
- The CLI command sends analytics to Toggl’s configured PostHog collector; analytics can be disabled with an environment flag.
- The flagged dependencies are Sentry instrumentation and a terminal prompt library; inspected entrypoints show no install scripts.
- The bundle’s credential handling uses Toggl API and accounts URLs for authenticated service requests.
- No inspected source showed command output being sent to an unrelated recipient or credentials being redirected to an unofficial gateway.
- The suspicious child process matches are delegated commands with inherited stdio; the inspected code did not show output collection or exfiltration.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-Cnxg1UIA.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.95.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.95 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.