@togglhq/cli@1.13.29
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe scanner’s command and network matches resolve to OAuth, product telemetry, and user-invoked CLI or skill operations. The package has no install hook, and the inspected credential flow does not show disclosure to an unrelated recipient.
Decision evidence
public snapshot- package.json exposes the CLI and program entrypoints and declares no install lifecycle hook; the root CLI is invoked by the user.
- The flagged agent integration code searches agent skill directories and forwards explicit skill, agent, global, copy, and confirmation options to the skills tool.
- Authentication defaults to Toggl’s accounts service; OAuth exchanges an authorization code there, and the staging host is selected only when the accounts URL is set to that host.
- The API token is read from the caller’s environment and selects token mode; inspected source contains no transfer of that token to an unrelated fixed recipient.
- CLI telemetry starts when the CLI runs, with Toggl product analytics and public Sentry privacy controls; this is runtime product behavior, not install-time disclosure.
- The prepared dependencies expose their expected Sentry SDK and skills CLI entrypoints; the flagged command execution is used to launch the selected CLI or skill operation.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-BuVQW29L.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.29.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.29 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.