@taskless/cli-nightly@0.11.3-20260922080130x5047148
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 1mo ago · by lpm-firewall-aiThe unrestricted endpoint override combined with automatic bearer-token forwarding is a concrete dangerous capability. It warrants a warning, but the default destination is package-aligned and no active malicious chain was found.
Decision evidence
public snapshot- The package exposes a CLI entrypoint and has no npm install lifecycle hook.
- A Taskless token is read from TASKLESS_TOKEN or the project auth file.
- TASKLESS_API_URL or a local config apiUrl can replace the default API destination without allowlist validation.
- The API client sends the retrieved token as a Bearer authorization header.
- Remote rule operations obtain that token before submitting requests.
- The default API URL is taskless.io and the risky forwarding requires an operator-controlled endpoint setting.
- No install-time hook, hidden payload execution, or destructive behavior was identified.
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.11.3-20260922080130x5047148.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.11.3-20260922080130x5047148 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.