@taskless/cli-nightly@0.13.0-20261016095010x7fe4d17
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 install lifecycle hook or credential redirect to an unofficial gateway. The flagged `eval` is example text, and agent skill setup is an explicit CLI operation.
Decision evidence
public snapshot- package.json lists build, generation, and test scripts; no npm install lifecycle hook was found.
- Login uses device authorization through the configured Taskless API base and polls for authorization; the source does not show a fixed unofficial credential gateway.
- Agent skills are installed by the explicit `taskless init` command into detected project directories.
- The `eval` match is an embedded example in a rule demonstrating detection of unsafe code, not executable package logic.
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-20261016095010x7fe4d17.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.13.0-20261016095010x7fe4d17 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.