@taskless/cli-nightly@0.13.3-20261021163833x46ca90e
Nightly build of [`@taskless/cli`](https://www.npmjs.com/package/@taskless/cli) — the same source and the same build, published from an unreleased commit on `main`.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe default endpoint is package-aligned, but an unrestricted API URL override controls where the CLI sends its saved Taskless bearer token. This is conditional credential exposure, so it warrants a warning rather than a publication block.
Decision evidence
public snapshot- The CLI uses the Taskless service by default, but accepts an API URL from the environment or its configuration without restricting the destination.
- It reads a saved access token from the project’s local Taskless authentication file.
- Authenticated API requests put that token in a bearer header for the selected API base URL.
- Normal authenticated CLI operations retrieve the saved token and pass it to API helpers.
- The package’s default API endpoint is app.taskless.io, and login is presented as authentication with taskless.io.
- The manifest has no install lifecycle hook; the credential risk requires an operator-supplied API URL override.
Source & flagged code
5 flaggedManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @taskless/cli-nightly@0.13.3-20261021163833x46ca90e.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.13.3-20261021163833x46ca90e 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.