eve@0.30.3
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection disproves the scanner’s install-time and host-fingerprint implications: this is a CLI/AI-agent framework with no lifecycle hooks, and the identified network path is scoped Vercel OIDC support. No concrete malicious chain was found.
Decision evidence
public snapshot- package.json has no preinstall/install/postinstall lifecycle hook.
- bin/eve.js runs only when the eve CLI is invoked; its spawn calls rebuild local workspace assets.
- mock-model-adapter.js is test-only, gated by NODE_ENV=test or EVE_MOCK_AUTHORED_MODELS=1.
- Vercel credential code reads explicitly named Vercel credentials for the sandbox integration.
- The hostname-bearing OIDC request is Vercel token refresh, not general host-data exfiltration.
Source & flagged code
13 flagged · loading sourcePackage source references dynamic require/import behavior.
bin/eve.jsView on unpkg · L8Package source references a known benign dynamic code generation pattern.
dist/src/compiled/gray-matter/index.jsView on unpkg · L43Findings
Affected versions and remediation
This report applies to eve@0.30.3.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.30.3 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.