@taskless/cli-nightly@0.12.1-20261012222432x8a86506
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 23d ago · by lpm-firewall-aiThe flagged entrypoint contains ordinary Taskless authentication and telemetry flows; the apparent payload execution match is example rule text, not runtime execution. No install hook or unconsented agent configuration mutation was identified.
Decision evidence
public snapshot- package.json lists build and development scripts, with no install lifecycle hook; dist/index.js is the runtime entrypoint.
- dist/index.js defaults authentication to the Taskless CLI service and uses TASKLESS_API_URL or saved configuration when set.
- The login flow requests a device code and polls for a token at that authentication endpoint; it saves the returned token locally after authorization.
- Agent directories are detected for setup, which runs through an explicit init flow with a location choice and confirmation before writing files.
- Telemetry is sent to the Taskless service and can be disabled with TASKLESS_TELEMETRY_DISABLED or DO_NOT_TRACK.
Source & flagged code
4 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsFindings
Affected versions and remediation
This report applies to @taskless/cli-nightly@0.12.1-20261012222432x8a86506.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.12.1-20261012222432x8a86506 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.