eve@0.79.0
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource inspection found no malicious behavior: the flagged process execution is part of direct CLI startup, and the inspected network and credential handling is directed to Vercel or performs local authentication checks. The scanner’s labels do not establish an attack in these files.
Decision evidence
public snapshot- The manifest exposes library and CLI entrypoints; its scripts are build and test tasks, with no install hook.
- The CLI runs when invoked directly and then starts the package CLI.
- Vercel OAuth endpoints are restricted to Vercel origins, and the credits request sends a token to Vercel AI Gateway.
- MCP skill resources are read through registered handlers with path segments checked against traversal.
- HTTP Basic authentication compares supplied credentials with the configured strategy and returns an authentication result.
Source & flagged code
8 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.79.0.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.79.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.