@apilift/cli@1.5.2
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe CLI permits an unrestricted HTTP or HTTPS API origin and sends its saved installation token to that destination during ordinary commands. This is a conditional credential-exposure risk, while the reviewed agent-session and process-inspection signals do not establish a separate attack.
Decision evidence
public snapshot- Linking saves the Apilift installation token locally, and ordinary commands pass the saved token to the API client.
- The client sends the token as a bearer credential; APILIFT_URL accepts any HTTP or HTTPS origin and supplies the client’s base URL.
- The flagged collector code locates local Codex and Claude session directories. The session-audit target is a tokenizer string fragment; its relevant code reads transcripts and writes an audit report.
- The manifest exposes CLI entrypoints. The inspected native-host and capture-server behaviors align with reading a configured extension origin and checking a local process start time.
Source & flagged code
5 flaggedFindings
Affected versions and remediation
This report applies to @apilift/cli@1.5.2.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.5.2 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.