@taskless/cli-nightly@0.13.0-20261014152447x60763fb
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 21d ago · by lpm-firewall-aiSource inspection confirmed user-invoked agent setup that writes package-owned references into project agent directories, so a warning is appropriate. The credential and dynamic-import scanner signals are explained by the Taskless device-code flow and a rule-check harness.
Decision evidence
public snapshot- The manifest exposes the CLI entrypoint and lists build scripts, including prebuild, but no npm install hook.
- The explicit `init` command is described as installing or updating Taskless skills, and its runner invokes the installer.
- The installer detects project agent directories and maps them to reference targets such as `.claude`, `.agents`, `.cursor`, and `.opencode`.
- On that command path, package-generated skill and command references are written to the selected targets and the install state is recorded under `.taskless`.
- Login polls the configured Taskless API base with a device code; its default is the Taskless CLI service, not a fixed unrelated gateway.
- The flagged dynamic import is in a rule-check harness that imports a supplied `checkFile` and calls its exported check function.
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-20261014152447x60763fb.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.13.0-20261014152447x60763fb 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.