eve@0.67.1
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 27d ago · by lpm-firewall-aiStatic inspection of package.json and the required entry, auth, fixture, and Next server files shows a user-invoked agent framework with no install lifecycle, no self-dependency chain, and credentials sent only to checked Vercel OAuth hosts. Shell and file tools exist as explicit agent capabilities, not as covert install behavior.
Decision evidence
public snapshot- package.json is eve 0.67.1 with build and test scripts only, no preinstall, install, or postinstall hook, and runtime dependencies are nitro and undici rather than a self-dependency.
- bin/eve.js resolves a local dist CLI entrypoint under the package root when the eve command is invoked.
- Vercel model auth refreshes tokens only against vercel.com or api.vercel.com after checking the OAuth endpoint origin.
- mock-model-fixtures.js selects fixture replies from in-memory prompt text and does not perform network or file side effects.
- HTTP basic auth compares a caller-supplied username and password locally with a timing-safe hash and does not forward the credential.
- The Next helper accepts only loopback server origins and starts the local eve binary for development.
- The framework includes user-invoked shell, file, and model-auth code, which is expected for an agent runtime and is not an install-time control-surface write.
Source & flagged code
11 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 · L2Source file is highly similar to a previously finalized malicious package; route for source-aware review.
Findings
Affected versions and remediation
This report applies to eve@0.67.1.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.67.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.