@togglhq/cli@1.13.130
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged bundle contains analytics that the README documents, including its collected fields and opt-out. The inspected command execution supports the documented, explicitly invoked skill setup flow; no malicious credential redirect or command-output exfiltration was established.
Decision evidence
public snapshot- The manifest declares the Toggl CLI entry point and no install lifecycle scripts.
- The README discloses command analytics fields, says arguments and output are not collected, and documents an opt-out.
- Analytics events contain command name, action, outcome, client, session ID, package version, and a classified error category.
- The default analytics destination is Toggl’s PostHog endpoint; the host is configurable through a PostHog-specific environment variable.
- A static scanner flagged command execution and possible output exfiltration, but the inspected `spawn` use runs the `skills` CLI for the documented skill setup feature with inherited stdio.
- The reviewed analytics code does not include command arguments or output in its event properties.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-R7s6-WWw.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.130.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.130 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.