@taskless/cli-nightly@0.13.0-20261015175549xf240f6f
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 20d ago · by lpm-firewall-aiSource inspection found no registry install hook or concrete attack behavior. The suspicious loader and credential-redirection signals resolve to a demo rule and a configurable Taskless API device-auth flow.
Decision evidence
public snapshot- package.json exposes the CLI bundle and lists build scripts, with no registry install lifecycle hook.
- The indicated .claude path is used for local agent detection; the user-invoked init command offers tool selection and writes Taskless skill metadata to selected locations.
- Authentication defaults to the Taskless service; changing the API destination requires an environment or configuration setting, and login uses a device-code flow.
- The eval example is embedded in a demo rule that teaches detection; it is not an executed payload.
Source & flagged code
4 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.0-20261015175549xf240f6f.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.13.0-20261015175549xf240f6f 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.