@taskless/cli-nightly@0.11.1-20260904165917x8feee4c
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 has no install lifecycle hook, and the inspected network request is an explicit Taskless CLI API operation. Static eval and payload-loader signals correspond to bundled dependencies and reference-rule text, not executable hidden payload behavior.
Decision evidence
public snapshot- The manifest has no preinstall, install, or postinstall hook.
- The CLI's rule-generation request uses a Taskless API route when the relevant command is invoked.
- The reference asset contains declarative example rules, including a test fixture that mentions eval.
- No hidden-code execution primitive was found; base64 helpers are bundled library code.
- No credential redirection, foreign agent-control mutation at install time, or self-dependency is present.
- File-writing behavior is tied to explicit CLI setup and rule-generation commands.
Source & flagged code
5 flaggedManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @taskless/cli-nightly@0.11.1-20260904165917x8feee4c.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.11.1-20260904165917x8feee4c 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.