@taskless/cli-nightly@0.13.0-20261016013447x784899c
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-aiThe static hints do not match executable attack behavior: the eval example is demonstration text, and authentication uses the configured Taskless device-code flow. The manifest has no install lifecycle hook, and the agent setup path is an explicit CLI command.
Decision evidence
public snapshot- The manifest’s scripts are build, generation, testing, and typechecking tasks; its runtime entrypoint is dist/index.js, with no install lifecycle hook.
- Authentication uses the configured Taskless API base for device authorization and token polling, and stores the returned token under the repository’s .taskless directory.
- The flagged eval(payload) text appears inside a bundled demonstration rule that teaches how to detect eval calls; it is not an executed payload loader.
- The agent integration excerpt maps supported project skill directories; setup is performed through the CLI’s explicit init command.
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-20261016013447x784899c.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.13.0-20261016013447x784899c 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.