eve@0.31.0
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection found no lifecycle execution or covert exfiltration chain. Scanner signals arise from an explicit CLI build fallback, test mock code, and package-aligned Vercel OIDC support.
Decision evidence
public snapshot- package.json has no preinstall, install, postinstall, or prepare hook.
- bin/eve.js runs child processes only when the user invokes the eve CLI, to build a source workspace.
- mock-model-adapter.js is test-only, gated by NODE_ENV=test or EVE_MOCK_AUTHORED_MODELS=1.
- The flagged hostname is included in a Vercel OIDC user-agent during authenticated token refresh, not harvested for unrelated exfiltration.
Source & flagged code
12 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.31.0.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.31.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.