@taskless/cli-nightly@0.11.2-20260911010750xea9cef8
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 high-risk primitive is transparent and command-gated, but it executes project code and can transmit an authentication bearer token to the configured service. The scanner's claimed api.example.com credential gateway is a demo fixture, not an active endpoint.
Decision evidence
public snapshot- The user-invoked runtime-rule harness dynamically imports and calls a project check file.
- Authenticated runtime-rule reconciliation sends its bearer token to the configured Taskless API.
- Runtime rules can be explicitly run without server verification using a danger-labelled flag.
- package.json has no preinstall, install, or postinstall hook.
- The default API endpoint is app.taskless.io; the scanner's api.example.com match is embedded demo fixture text.
- Without the explicit flag, anonymous, unauthenticated, or unverified runtime rules are withheld.
Source & flagged code
6 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.2-20260911010750xea9cef8.
See all versions of @taskless/cli-nightly for other recorded verdicts.
- Review the evidence and your use of @taskless/cli-nightly@0.11.2-20260911010750xea9cef8 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.