eve@0.79.1
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe source inspection found no install lifecycle hook or concrete malicious behavior. Scanner flags are explained by package-local CLI build logic and provider-aligned Vercel authentication; the other required flagged paths implement resource serving and credential verification.
Decision evidence
public snapshot- The manifest exposes Eve’s CLI and runtime entrypoints and declares build, development, and test scripts; no install lifecycle hook was found.
- The CLI spawns package-local build tools only to prepare a missing or stale CLI, and runs the CLI when invoked directly.
- Vercel OAuth endpoints are restricted to Vercel hosts; the gateway check sends a bearer token to Vercel AI Gateway as part of that provider flow.
- The MCP skills module registers handlers to list and read skill resources.
- HTTP Basic authentication checks the supplied credentials against the configured strategy and returns an authenticated principal.
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.1.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.79.1 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.