@apilift/cli@1.4.18
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource supports a warning for first-party agent plugin installation and subsequent automatic refresh, rather than malware classification. Explicit setup, ownership checks, and the absence of npm install hooks prevent a confirmed install-time agent hijack finding.
Decision evidence
public snapshot- package.json has no npm install lifecycle hooks or runtime self-dependency.
- The explicit setup continue command installs the plugin only for a linked installation with an agent identity.
- The installer stages an Apilift-owned plugin and refuses to replace an unmanaged plugin directory.
- The installer writes the personal plugin marketplace and installs or updates and enables apilift@personal.
- Eligible global CLI installations automatically check for updates unless disabled; updates refresh plugins for linked agents.
- The indicated collector and session-audit agent locations are tokenizer vocabulary entries, not configuration writes.
- Native-host requests require an extension handshake; inspected behavior does not establish remote payload execution or credential theft.
Source & flagged code
4 flaggedPackage source references child process execution.
dist/apilift.jsView on unpkg · L30791Manifest-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.18.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.4.18 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.