@togglhq/cli@1.13.76
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection found no install-time hook or confirmed attack behavior. Scanner matches correspond to normal OAuth, product analytics, browser opening, and explicit CLI setup or update operations.
Decision evidence
public snapshot- package.json exposes the CLI and declares build and development scripts, with no install lifecycle hook; the inspected runtime dependencies also contain no install hook.
- OAuth runs through the explicit auth command, exchanges its code with the configured Toggl Accounts endpoint, and saves the returned profile locally.
- Analytics sends a limited set of command and outcome fields to Toggl’s PostHog project; the inspected payload omits command arguments and results, and analytics can be disabled.
- The flagged dependency paths contain CLI prompt code and Sentry/OpenTelemetry exports or instrumentation, consistent with their declared package roles.
- The shell calls open the OAuth URL or run explicit setup and update commands with inherited standard I/O; no command-output upload path was found.
- The OAuth endpoint defaults to Toggl Accounts and can be configured; no fixed unofficial credential gateway or credential redirection was found.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-BklQ8ONG.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.76.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.76 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.