@apilift/cli@1.5.1
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the inspected high-risk matches resolve to local transcript lookup, tokenizer data, and a bearer-protected loopback service. The source inspected does not establish a concrete attack surface, so the static scanner signals do not support a block.
Decision evidence
public snapshot- package.json declares CLI entrypoints and no lifecycle hooks.
- The collector resolves Codex and Claude session directories for transcript lookup; the inspected code does not show an agent configuration write.
- The session-audit match is tokenizer vocabulary data, not an agent configuration operation.
- The CLI uses environment variables for its configurable runtime and plugin paths.
- The native-host file is a bundled CLI entrypoint.
- The capture server requires a bearer token and uses a loopback address.
Source & flagged code
5 flaggedFindings
Affected versions and remediation
This report applies to @apilift/cli@1.5.1.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.5.1 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.