@taskless/cli-nightly@0.11.4-20260927201224x86799ef
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 package is a first-party CLI that mutates agent skill directories only after the taskless command runs, which is a guarded agent-capability change rather than an install-time hijack. No lifecycle hook, remote payload, or credential exfiltration was found in that path.
Decision evidence
public snapshot- package.json defines a taskless bin at dist/index.js and has no preinstall, install, or postinstall hook.
- The init command installs or updates bundled Taskless skills and commands into detected agent directories such as .claude, .cursor, .opencode, and .agents, with .agents as the fallback.
- A bare CLI invocation with only known flags can enter the interactive install path; scripted installs are the explicit taskless init command.
- Agent directory writes are reached from the CLI command dispatcher, not from an npm lifecycle script.
- The written content is this package's own skill and command stubs for the Taskless product, not a remote payload.
- No credential harvesting, shell eval, or self-install of another release was found in the install path.
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.11.4-20260927201224x86799ef.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.11.4-20260927201224x86799ef 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.