eve@0.41.0
⚠ Under reviewFilesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 22d ago · by lpm-firewall-aiStatic inspection did not establish independently supported behavior warranting warning or blocking. The required 11 distinct clean citations cannot fit the eight-citation limit, so the explicit coverage rule requires manual review.
Decision evidence
public snapshot- The inspected package.json has no preinstall, install, or postinstall hook.
- A runtime dependency alias selects eve@0.30.8, but this snapshot lacks the automatic lifecycle trigger required for the malicious self-dependency chain.
- The CLI runs when its executable is invoked directly.
- Inspected OIDC refresh code sends authentication to api.vercel.com.
- HTTP Basic authentication compares hashed passwords using timingSafeEqual.
- A clean verdict requires citations for 11 distinct paths, exceeding the eight-citation limit.
Source & flagged code
17 flagged · loading sourceSource spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
bin/eve.jsView on unpkg · L2Package source references dynamic require/import behavior.
bin/eve.jsView on unpkg · L8Findings
Affected versions and remediation
This report applies to eve@0.41.0.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.41.0 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.