@taskless/cli-nightly@0.11.1-20260907165206x0553dfb
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-aiNo install lifecycle, hidden payload loader, credential redirection, or covert exfiltration was confirmed. The explicit unverified runtime-code path remains a meaningful dangerous capability and warrants a warning.
Decision evidence
public snapshot- The CLI dynamically imports and invokes project runtime-rule check.ts code.
- The check command exposes an explicit flag to run unverified runtime code.
- Authenticated default execution sends runtime-rule signatures to the service and runs only rules it returns as allowed.
- package.json has no preinstall, install, postinstall, or other lifecycle hook.
- Runtime rules are skipped by default when anonymous, unauthenticated, or without a GitHub remote.
- The decoded base64 uses are library YAML/JWT handling, not a hidden payload loader.
Source & flagged code
5 flaggedPackage source references a known benign dynamic code generation pattern.
dist/recipes-CvKZ_SFw.jsView on unpkg · L173Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
Findings
Affected versions and remediation
This report applies to @taskless/cli-nightly@0.11.1-20260907165206x0553dfb.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.11.1-20260907165206x0553dfb 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.