@togglhq/cli@1.13.74
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection found no confirmed attack behavior. The scanner’s network, credential, and subprocess signals map to the CLI’s service requests, limited analytics, browser opening, and user-invoked setup or update functions.
Decision evidence
public snapshot- The manifest exposes a CLI and JavaScript entrypoints, with no install lifecycle hook.
- Authentication defaults to Toggl’s service; alternate API hosts come from explicit options or environment settings, and API keys are sent to the selected API.
- Analytics can be disabled and records command identifiers, outcomes, and limited session metadata at Toggl’s PostHog endpoint.
- Subprocesses open the login URL, run the skills installer, or perform a requested update; they inherit terminal I/O rather than collecting command output.
- The inspected dependencies provide Sentry instrumentation and a separately invoked skills CLI; their referenced source does not establish an attack.
- The flagged network, environment, and child-process APIs have product-aligned uses in the inspected source; no unrelated credential recipient or command-output transfer was identified.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-vWv4sVQX.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.74.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.74 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.