eve@0.80.0
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete malicious behavior in the flagged files. The scanner findings correspond to guarded product functions, so the package is clean.
Decision evidence
public snapshot- The manifest exposes a CLI and library entrypoints; its scripts show build and development tasks, not an install hook.
- The CLI runs when directly invoked and then loads the CLI module.
- Vercel OAuth endpoints are restricted to vercel.com and api.vercel.com.
- HTTP Basic authentication checks supplied credentials against the configured strategy.
- The GitHub shell requires declared write permission and rejects command targets outside declared repositories.
- MCP skills are served through validated skill paths and file reads; the inspected module contains no shell or network calls.
Source & flagged code
9 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.jsFindings
Affected versions and remediation
This report applies to eve@0.80.0.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.80.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.