@apilift/cli@1.4.32
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install hook, and inspected runtime excerpts show local session discovery, caller-invoked audit processing, and a loopback capture listener. The flagged agent integration excerpts do not establish unauthorized configuration changes or credential transfer, so the scanner hints do not support a malicious verdict.
Decision evidence
public snapshot- package.json exposes CLI entrypoints and declares no install lifecycle hook.
- The collector reads Codex and Claude session directories to locate transcripts.
- The native host reads framed input from standard input.
- The capture server binds to loopback, limiting its listener to the local machine.
- The CLI accepts APILIFT_URL as an HTTP(S) service origin, defaulting to apilift.dev.
- The session-audit target excerpt is a string table; the audit entrypoint processes caller-provided arguments.
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.32.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.4.32 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.