@taskless/cli-nightly@0.11.1-20260904032807xf08fd11
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 static evidence, but its remote-backed runtime-rule executor is a meaningful code-execution capability. It warrants a warning rather than a publication block because activation is user-commanded and lifecycle installation is absent.
Decision evidence
public snapshot- The check feature dynamically imports and invokes project runtime-rule code.
- Authenticated checks can copy server-approved runtime rules into the project before execution.
- The CLI sends usage telemetry to a fixed Taskless endpoint.
- package.json has no preinstall, install, or postinstall hook.
- Runtime execution is skipped in anonymous mode and requires either authentication or an explicit dangerous flag.
- The inspected credential flow uses the Taskless API default and stores tokens in a repository-local file with restrictive permissions.
Source & flagged code
5 flaggedPackage source references a known benign dynamic code generation pattern.
dist/recipes-o-WV5UrX.jsView on unpkg · L172Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
Findings
Affected versions and remediation
This report applies to @taskless/cli-nightly@0.11.1-20260904032807xf08fd11.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.11.1-20260904032807xf08fd11 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.