@apilift/cli@1.4.33
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install hook or runtime self-dependency, and inspected credential handling does not establish a hidden fixed-gateway redirect. The scanner’s flagged agent locations resolve to local session path selection and tokenizer vocabulary data, while the collector delivery excerpt shows measurement submission.
Decision evidence
public snapshot- package.json declares CLI entrypoints but no install lifecycle hook; its runtime dependencies do not include itself.
- The flagged collector location selects local Codex session paths; its delivery code submits execution measurements and baselines using an installation token.
- The flagged session-audit location contains tokenizer vocabulary fragments, not agent configuration writes.
- The API client sends its supplied token in an authorization header, and the capture server binds to loopback.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/apilift.jsView on unpkg · L31120Manifest-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.33.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.4.33 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.