@apilift/cli@1.5.12
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior. The scanner’s dynamic-execution and credential-redirection signals correspond to a fixed process-check worker, service authentication to the Apilift API, and analytics constrained to a validated host and key.
Decision evidence
public snapshot- The manifest exposes four user-invoked command entrypoints and lists build and test scripts; no install lifecycle hook was found.
- The flagged worker evaluates fixed process-check code that queries Windows process start times.
- The stored installation token is used as a bearer token with the Apilift API, whose default host is the Apilift service.
- Analytics sends queued events only when service-provided settings enable it and the host and project key pass fixed checks.
- The native host checks its caller origin; the inspected audit, capture-server, keyring, pricing, and schema-validator sources show package-aligned runtime behavior.
Source & flagged code
5 flaggedFindings
Affected versions and remediation
This report applies to @apilift/cli@1.5.12.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.5.12 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.