@taskless/cli@0.13.2
[](https://www.npmjs.com/package/@taskless/cli) [](https://github.com/taskless/cli/actions/workflows/val
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe default endpoint and explicit device login are consistent with the CLI’s service, but the unrestricted configurable base URL also receives existing session credentials. This supports a warning for conditional credential exposure, not a finding of malicious default exfiltration.
Decision evidence
public snapshot- Saved or environment-provided Taskless tokens are used for authenticated API requests.
- The API base URL can come from TASKLESS_API_URL or a saved apiUrl, with no destination allowlist shown.
- The bearer token is sent to the selected API base URL for authenticated requests.
- The default API endpoint is the Taskless service, and login uses an explicit device authorization flow.
- The package manifest has no install lifecycle hooks; its bin and module point to the CLI entrypoint.
- The default authentication endpoint is https://app.taskless.io/cli.
Source & flagged code
5 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @taskless/cli@0.13.2.
See all versions of @taskless/cli for other recorded verdicts.
- Review the evidence and your use of @taskless/cli@0.13.2 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.