@apilift/cli@1.5.14
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe source review found configured operational analytics and bounded local helpers, not a concrete attack. The scanner's dynamic-execution lead resolves to bundled process-monitoring code, while the QuickSilver Pro match is pricing metadata rather than credential forwarding.
Decision evidence
public snapshot- The manifest exposes CLI binaries and lists build, typecheck, and test scripts; it has no install lifecycle hook.
- The CLI starts its analytics collector after command handling, supports a disable flag, and limits event properties to operational fields.
- The collector checks the analytics enabled flag, fixed host, and project-key format before sending; its event payload includes account and workspace identifiers.
- The capture server requires a bearer token. Its eval-enabled worker runs bundled source that queries Windows process start times.
- The native helper uses bearer-authenticated loopback requests, and the session audit entrypoint processes command-line arguments.
- The flagged QuickSilver Pro host appears in provider pricing metadata; the inspected dependencies provide keyring loading, pricing data, and JSON Schema validation.
Source & flagged code
5 flaggedFindings
Affected versions and remediation
This report applies to @apilift/cli@1.5.14.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.5.14 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.