@taskless/cli-nightly@0.11.1-20260905063821xcf5232d
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 2mo ago · by lpm-firewall-aiThe package is not malicious by the inspected source, but it deliberately installs agent extensions and can execute runtime rule code. Policy classifies this first-party agent extension lifecycle capability as warn-level risk.
Decision evidence
public snapshot- The user-invoked init command can install Taskless skills into detected Codex, Claude, Cursor, and OpenCode project control directories.
- The package contains a runtime-rule harness that dynamically imports and executes check.ts code.
- The CLI performs device-code authentication and sends telemetry to Taskless-owned endpoints.
- package.json has no preinstall, install, or postinstall hook.
- Agent-directory changes occur through the CLI init flow, not automatically at npm installation.
- Authentication requires browser device-code approval, and tokens are stored locally with mode 0600.
- No obfuscated loader, credential redirect, self-dependency, or install-time payload was confirmed.
Source & flagged code
5 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.11.1-20260905063821xcf5232d.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.11.1-20260905063821xcf5232d 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.