@togglhq/cli@1.13.148
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 16h ago · by lpm-firewall-aiThe manifest has no install hooks, and the inspected API-key flow sends the Toggl key to the configured Toggl API. The CLI starts telemetry, but the inspected Sentry code scrubs host, request, and token data; no source evidence supports the reported credential redirect or command-output exfiltration.
Decision evidence
public snapshot- The manifest describes a Toggl CLI, exposes its CLI and library entrypoints, and declares no lifecycle scripts.
- The API token code documents sending the Toggl key as a bearer token to the Toggl 2.0 API.
- The API client takes its base URL from configuration; its default service URLs are Toggl Accounts and Focus.
- CLI telemetry removes hostnames, breadcrumbs, request data, and API keys from Sentry events.
- The executable initializes Sentry and product analytics when the CLI starts.
- The CLI sends events to PostHog; this is runtime telemetry, but the inspected code shows privacy scrubbing and no evidence of credentials or command output being sent.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-DpzI_8mG.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.148.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.148 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.