@apilift/cli@1.4.35
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe inspected package manifest has no install hook, and the flagged locations did not establish an attack chain. The static hints for credential redirection and remote code execution were not confirmed by inspected source evidence.
Decision evidence
public snapshot- The manifest exposes CLI entrypoints and declares no install lifecycle hooks.
- The collector integration location reads Codex and Claude session directories for collection.
- The session-audit integration location is inside a token data table; it does not configure an agent.
- The CLI uses the package's apilift.dev site by default and permits an explicit HTTP(S) site override.
- The capture server evaluates a worker source string locally; inspected evidence does not show remote code being supplied.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/apilift.jsView on unpkg · L31202Findings
Affected versions and remediation
This report applies to @apilift/cli@1.4.35.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.4.35 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.