@togglhq/cli@1.13.69
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. The scanner’s credential and subprocess signals map to API authentication, browser launching, and delegated CLI execution; the inspected source does not show a fixed unofficial gateway or command-output exfiltration.
Decision evidence
public snapshot- package.json exposes the CLI and library entrypoints and has no install lifecycle hook.
- The CLI entrypoint parses user-supplied arguments; API token mode reads TOGGL_API_TOKEN and sends it as a bearer credential through the selected API client.
- The default API destinations are Toggl services. The API URLs can be overridden through environment settings, so the source does not establish a hidden, fixed credential recipient.
- The flagged subprocess paths open the authentication browser or run the skills CLI with inherited standard streams; the inspected excerpts do not show command-output collection or exfiltration.
- The required dependency excerpts identify Sentry’s instrumentation SDK and the skills CLI, including their normal module entrypoints.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-CgO1wpBJ.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.69.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.69 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.