@taskless/cli-nightly@0.13.4-20261029223938xcd2357c
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-related code is in a launcher flow for installing the project's pinned Taskless CLI; it temporarily supplies the project npm configuration to npm and removes the copy afterward. The manifest declares no install lifecycle hook, and the reviewed code does not show credentials being sent to an unrelated host.
Decision evidence
public snapshot- The manifest has no install, preinstall, or postinstall hook; its scripts are build and development commands.
- The package exports dist/index.js as its CLI entry point.
- The embedded launcher template describes installing the project-pinned Taskless CLI on first run, then running it from the project cache.
- The launcher copies the project .npmrc into a temporary install directory for npm, then removes that copy after npm ci.
- That npm ci invocation disables package scripts, audit, and funding requests.
- The launcher starts the cached CLI with the user's arguments and inherited environment.
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-20261029223938xcd2357c.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.13.4-20261029223938xcd2357c 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.