@apilift/cli@1.4.31
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found no install hook or unconsented credential transfer to an unrelated recipient. The flagged agent and execution signals resolve to explicit setup, session analysis, filtered telemetry, and a local authenticated browser helper.
Decision evidence
public snapshot- The manifest exposes CLI entrypoints and lists build, typecheck, and test scripts; it has no install lifecycle hook.
- Setup directs the user to sign in and provide a one-time code, sends it to the configured Apilift service, and saves the returned installation token locally.
- Session lookup is scoped to agent session locations; the flagged audit location is a token-list fragment, while the audit command requires a caller-supplied session and writes a report.
- Telemetry filters event properties through an allowlist and uploads only with an enabled identity restricted to the configured collector host.
- The native host checks its registered browser caller, and the local capture server binds to loopback and requires a bearer token.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/apilift.jsView on unpkg · L31118Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/apilift.jsView on unpkgFindings
Affected versions and remediation
This report applies to @apilift/cli@1.4.31.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.4.31 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.