@taskless/cli-nightly@0.11.1-20260907181107x9edb1f0
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 static hints are explained by normal CLI functionality: device authentication, telemetry, and guarded runtime-rule execution. Source inspection found no lifecycle hook, payload loader, credential redirect, or malicious persistence.
Decision evidence
public snapshot- The CLI includes an explicit runtime-rule harness that dynamically imports a selected rule file.
- It stores a successful device-login token in the project's .taskless directory.
- The package includes a JSON reference file describing rule-generation protocol and layout.
- package.json has no preinstall, install, postinstall, or self-dependency.
- Runtime-rule execution is labeled as executing untrusted code and is gated behind --dangerously-run-scripts or signed reconciliation.
- Auth requests target the Taskless service and token storage uses mode 0600.
- No credential exfiltration, hidden payload reconstruction, foreign agent-config mutation, or destructive install behavior was found.
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-20260907181107x9edb1f0.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.11.1-20260907181107x9edb1f0 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.