@taskless/cli-nightly@0.13.4-20261026181356xfcb2a39
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 8d ago · by lpm-firewall-aiSource inspection found no install hook or evidence of the reported credential redirection. The executable’s inspected credential flow uses the configured Taskless API for device authorization and stores the returned token in the project directory.
Decision evidence
public snapshot- package.json lists build and development scripts but no install lifecycle hook; the executable entry is dist/index.js.
- The CLI uses the Taskless service by default and allows an API URL to be set through configuration or the environment.
- Login requests a device code, waits for authorization, then saves the returned token for the selected project.
- The saved token is kept under the project’s .taskless directory.
- The inspected tsx dependency is a TypeScript runner, and its loader imports its runtime modules.
- The inspected ast-grep optional packages are platform-specific native tool packages.
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.4-20261026181356xfcb2a39.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.13.4-20261026181356xfcb2a39 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.