@togglhq/cli@1.13.103
Toggl CLI for Toggl 2.0 API operations.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution belongs to an explicit skill setup/update command, and the inspected GitHub credential flow targets GitHub's own API. Runtime analytics are disclosed in the README, exclude command arguments and output, and have an opt-out.
Decision evidence
public snapshot- The manifest routes the CLI to build/cli.js and exposes JavaScript entrypoints through build/index.js and build/program.js.
- The README discloses runtime analytics, says command arguments and output are not collected, and provides a TOGGL_PRODUCT_ANALYTICS=off setting.
- The skills subprocess is reached through the explicit setup/add or sync/update commands.
- The skills dependency sends a discovered GitHub token as a Bearer token only to api.github.com for a repository tree request.
- No install lifecycle hooks are declared in the manifest.
- The inspected credential flow does not send the GitHub token to add-skill.vercel.sh or skills.sh.
- The package describes the skill setup command as installing its packaged toggl-cli skill.
Source & flagged code
5 flaggedPackage source references child process execution.
build/program-tmBDubHd.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @togglhq/cli@1.13.103.
See all versions of @togglhq/cli for other recorded verdicts.
- Review the evidence and your use of @togglhq/cli@1.13.103 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.