@taskless/cli-nightly@0.12.0-20260930005007x106186c
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 1mo ago · by lpm-firewall-aiThe inspected source exposes an explicit user-command capability to modify project-local AI-agent instructions, which the supplied policy classifies as warning-worthy. No npm install hook or concrete malicious behavior supports publication blocking.
Decision evidence
public snapshot- The explicit init command invokes setup without a confirmation prompt.
- Setup detects project-local agent directories, including .claude, and writes Taskless skill stubs.
- Repeated setup updates recorded installation state and removes previously recorded obsolete skills.
- Interactive setup lets users select agent targets; this does not authorize npm lifecycle mutation.
- package.json has no preinstall, install, or postinstall hook and no runtime self-dependency.
- The inspected agent setup is activated through CLI commands, rather than npm installation.
- The writes install package-owned Taskless skills and commands; no covert credential export or remote payload execution was established.
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.12.0-20260930005007x106186c.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.12.0-20260930005007x106186c 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.