@taskless/cli-nightly@0.13.4-20261028215052x01251d2
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 5d ago · by lpm-firewall-aiThe credential flow targets the configured Taskless service, which defaults to app.taskless.io. The added launcher installs a pinned Taskless package with npm scripts disabled and is generated through the user-invoked init flow.
Decision evidence
public snapshot- The manifest exposes the CLI and lists build and generation scripts; no install lifecycle script is declared.
- The CLI uses app.taskless.io by default and accepts an API URL from the environment or its config file.
- The CLI sends its bearer token to the API client using that resolved service URL.
- On a cache miss, the project launcher copies the project’s npm configuration and runs npm ci with install scripts disabled.
- The launcher requires a recorded package version and starts that version; its files are created by the interactive init flow, which can be cancelled.
- The feedback recipe tells the user to review the payload and explicitly approve before sending.
Source & flagged code
5 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @taskless/cli-nightly@0.13.4-20261028215052x01251d2.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.13.4-20261028215052x01251d2 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.