@togglhq/cli@1.13.38
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged runtime paths resolve to ordinary Toggl authentication, metadata-limited analytics, and explicitly invoked first-party skill setup. The scanner signals do not establish an attack.
Decision evidence
public snapshot- package.json declares the CLI entrypoint and has no install lifecycle hook.
- The CLI runs from process arguments and exports the program; it does not run the agent skill installer at startup.
- Toggl API token mode sends requests through the CLI client, and OAuth defaults to Toggl Accounts.
- Analytics capture is gated and records command names, actions, outcomes, and error categories rather than arguments or results.
- Agent skill installation is exposed as an explicit CLI command; the installer writes packaged skill files after that command is invoked.
- The inspected dependency manifests and entrypoints show ordinary Sentry instrumentation and the skills installer, with no install hook in either manifest.
- The CLI initializes telemetry at startup, and analytics are enabled by default unless disabled; inspected capture code limits event properties to command metadata.
- The explicit skills command can write files into an agent directory, but it is a user-invoked first-party skill setup operation.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-C2e4goEY.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.38.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.38 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.