@apilift/cli@1.5.8
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. The flagged dynamic evaluation is used for a fixed local Windows process helper, and analytics is gated by validated service-provided settings and identity.
Decision evidence
public snapshot- package.json exposes four CLI entrypoints and has no install lifecycle hook.
- Analytics requires a valid installation identity and server-provided enablement, host, and project key; it refreshes identity through the configured Apilift API and sends filtered event batches to the returned host.
- The dynamic worker code is a local Windows process helper that receives a process ID; the capture server excerpt shows a fixed PowerShell helper rather than remote response code being executed.
- The auxiliary entrypoints and inspected dependencies match native-host origin checks, session auditing, keyring support, model pricing, and schema validation.
Source & flagged code
5 flaggedFindings
Affected versions and remediation
This report applies to @apilift/cli@1.5.8.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.5.8 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.