@apilift/cli@1.7.0
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source shows default background analytics after CLI commands, with an environment-variable opt-out but no clear in-package disclosure. The transmitted data is limited to command metadata and service-assigned identifiers in the inspected code, so this warrants a telemetry warning rather than a malicious verdict.
Decision evidence
public snapshot- The manifest has no install lifecycle scripts and exposes the CLI through dist/apilift.js.
- After a CLI command finishes, the CLI starts a background collector unless the collector is disabled by environment variable.
- Telemetry events include command, purpose, outcome, duration, stage and agent; batches also include account, workspace and installation IDs.
- The collector sends queued analytics to eu.i.posthog.com when the service enables analytics for the installation.
- The collector requires the service-provided analytics setting to be enabled and restricts its host to the EU PostHog endpoint.
- The reviewed telemetry fields contain command metadata and service-assigned IDs; no credential values or command arguments are shown in the reported payload.
- The collector can be disabled with APILIFT_COLLECTOR_DISABLED=1.
- No install hook or automatic install-time network contact is declared.
Source & flagged code
5 flaggedFindings
Affected versions and remediation
This report applies to @apilift/cli@1.7.0.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.7.0 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.