@taskless/cli-nightly@0.12.1-20261012211347xa36bab1
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 23d ago · by lpm-firewall-aiThe manifest has no npm install lifecycle hook, and the flagged eval sample is part of a bundled demo rule rather than executable payload code. The agent setup path is user initiated and includes selection and confirmation prompts; no concrete malicious behavior was established.
Decision evidence
public snapshot- package.json lists build, generation, and test scripts; the inspected manifest has no npm install lifecycle hook.
- package.json points the CLI entrypoint to dist/index.js.
- The bundled eval example is inside a demo rule string, not an executed call.
- Agent integration detects project tool directories, then asks which tools to enable Taskless for.
- The init flow obtains confirmation before writing selected agent integration files.
Source & flagged code
4 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsFindings
Affected versions and remediation
This report applies to @taskless/cli-nightly@0.12.1-20261012211347xa36bab1.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.12.1-20261012211347xa36bab1 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.