@apilift/cli@1.5.13
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior. The scanner’s dynamic-evaluation and credential-redirection hints do not match the inspected code: evaluation serves a local process check, and the analytics key and recipient are constrained by account configuration and a fixed host.
Decision evidence
public snapshot- package.json exposes CLI entrypoints and lists build and test scripts, with no install lifecycle hook.
- The flagged dynamic worker checks a Windows process start time using a local PowerShell script.
- Analytics sends are gated by the linked account’s enabled setting and use the fixed EU PostHog host with a validated project key.
- Inspected entrypoints and dependency snapshots match native-host, audit, pricing, keyring, and JSON-schema functions; no concrete attack behavior was found.
Source & flagged code
5 flaggedFindings
Affected versions and remediation
This report applies to @apilift/cli@1.5.13.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.5.13 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.