@taskless/cli-nightly@0.13.0-20261015214632x55b82fe
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 manifest has no install lifecycle hook, and the inspected runtime behavior is consistent with a user-invoked CLI. The scanner matches correspond to embedded analysis examples rather than active credential redirection or hidden code execution.
Decision evidence
public snapshot- The manifest exposes the CLI bundle and lists no install lifecycle hook.
- Login uses the Taskless service by default and exchanges a device code; the service URL can be overridden through local configuration or an environment setting.
- Agent setup asks which tools to enable and confirms planned changes before writing files.
- The execution and credential-related matches are embedded static-analysis examples and sample inputs, not active execution or credential forwarding.
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-20261015214632x55b82fe.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.13.0-20261015214632x55b82fe 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.