@taskless/cli-nightly@0.13.0-20261016085136x826cf88
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 flagged code supports normal CLI behavior rather than a concrete attack. The scanner's credential and payload findings are not substantiated by the inspected source.
Decision evidence
public snapshot- The manifest has no preinstall, install, or postinstall hook; its entrypoint is the CLI bundle.
- The CLI sends its bearer token through a client whose base URL comes from the Taskless API configuration, with the Taskless service URL as fallback.
- Agent skill files are written by an explicit setup routine that detects project agent directories; the flagged location is a detector entry.
- The apparent eval payload is embedded in a sample rule explaining why eval should be flagged, not executed by the CLI.
- The static credential redirect finding is not established by the inspected code: the API destination is configurable and defaults to the Taskless service endpoint.
- The payload-loader finding is not established: the inspected eval example is documentation content embedded in the bundle.
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-20261016085136x826cf88.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.13.0-20261016085136x826cf88 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.