@togglhq/cli@1.13.23
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection did not confirm the scanner's credential-redirection or command-output exfiltration claims. The credential flow uses configured Toggl API URLs, while the analytics and dependency matches are consistent with the CLI and SDK functionality shown in source.
Decision evidence
public snapshot- package.json exposes the CLI and program entrypoints and contains build and development scripts; no install lifecycle hook appears in its inspected scripts.
- The flagged credential flow defaults to Toggl production APIs, exchanges an authorization code with the configured Accounts API, and stores the resulting tokens with that API URL.
- The environment can select API URLs, and the CLI uses those configured URLs for authentication and subsequent requests; source inspection found no fixed unrelated credential recipient.
- The agent-related match is a skills-directory search path in the dependency CLI, not evidence of an install-time agent configuration write.
- The flagged Sentry paths are SDK exports and a Fastify request-span symbol; the skills dependency manifest has build and prepare scripts but no install hook.
- Scanner labels for credential redirection and command-output exfiltration are not supported by the inspected source paths.
- Product analytics uses the Toggl PostHog project and sends tool invocation event properties to its configured collector; the inspected send body does not establish command-output or credential transfer.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-CHU6dMAq.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.23.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.23 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.