@apilift/cli@1.8.4
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe source shows runtime analytics for CLI activity and a collector that starts by default; the reviewed event data includes command and runtime metadata. I found no evidence that the flagged dynamic worker executes remote code or that credentials are redirected, so this is suspicious telemetry rather than a malicious attack.
Decision evidence
public snapshot- On eligible CLI commands, the package starts its background collector by default; disabling it requires APILIFT_COLLECTOR_DISABLED=1.
- The analytics module defines events for CLI commands, setup, discovery, task observation, and delivery health.
- The CLI records command names, purpose, outcome, duration, agent, platform, and dispatch status in a finished-command analytics event.
- The manifest has no lifecycle scripts; its scripts are build and test commands.
- The reviewed dynamic worker code runs a fixed PowerShell process check to identify Windows process start times; it does not execute remote response content.
- The manifest exposes CLI binaries and a single package entry point.
Source & flagged code
6 flaggedFindings
Affected versions and remediation
This report applies to @apilift/cli@1.8.4.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.8.4 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.