@togglhq/cli@1.13.67
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe scanner’s command execution signal maps to opening the user’s Toggl authentication URL, and the inspected source does not establish command-output exfiltration or credential theft. Default analytics sends allowlisted invocation metadata to the Toggl-configured collector and has an environment opt-out; the inspected dependency entrypoints show ordinary SDK and CLI behavior.
Decision evidence
public snapshot- package.json exposes a CLI entrypoint and has no install lifecycle hook; its scripts are build and development commands.
- The CLI initializes telemetry when run, while OAuth code exchange sends an authorization code to the configured Toggl Accounts API.
- Analytics can be disabled with TOGGL_PRODUCT_ANALYTICS; invocation events use an allowlisted set of metadata and are sent to the configured PostHog host.
- The flagged shell execution opens the authentication URL in the system browser; inspected code does not show command output being transmitted.
- The inspected dependencies are Sentry instrumentation exports and the skills CLI; their cited entrypoints show no malicious behavior.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-BIMbFXA3.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.67.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.67 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.