eve@0.59.0
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source matches a user-invoked Vercel agent framework: no install hooks, and flagged files are first-party OAuth, telemetry, and vendored SDKs. The CLI and self-modification extension stay dual-use, and oversized compiled vendor trees could not be fully analyzed, so this stays a warning rather than clean or a block.
Decision evidence
public snapshot- First-party self-modification extension is registered in package metadata and can edit files and call GitHub when that product path runs.
- The eve CLI bootstraps with spawn and dynamic import and posts CLI telemetry to Vercel unless the user disables it.
- Vercel login refreshes OAuth tokens against vercel.com and ai-gateway.vercel.sh and stores session material under the user eve auth directory.
- Oversized minified vendor bundles embed Vercel Blob and OpenAI SDKs and cannot be fully reviewed line by line.
- The user-invoked agent CLI remains dual-use process, credential, and network capability even though npm install does not run a lifecycle hook.
- package.json has no preinstall, install, or postinstall scripts.
- Published runtime dependencies are only nitro and undici; the eve@0.30.8 alias is a named devDependency.
- HTTP basic auth only compares local credentials with a timing-safe hash.
- Inspected hosts in flagged files are first-party Vercel, OpenAI, and GitHub product endpoints.
- CLI, OAuth, and telemetry run after the user invokes eve, not at registry install.
Source & flagged code
13 flagged · loading sourcePackage contains a critical-looking secret pattern.
dist/src/compiled/@vercel/blob/index.jsView on unpkg · L28RSA private key in dist/src/compiled/@vercel/blob/index.js
dist/src/compiled/@vercel/blob/index.jsView on unpkg · L28Findings
Affected versions and remediation
This report applies to eve@0.59.0.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.59.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.