eve@0.67.0
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 27d ago · by lpm-firewall-aieve 0.67.0 is a user-invoked agent framework whose install metadata has no lifecycle hook and whose inspected auth, CLI, mock, and Next entrypoints stay package-aligned. Credential use is bound to Vercel OAuth origins or local comparison, so no concrete attack surface remains.
Decision evidence
public snapshot- package.json names the eve CLI bin and only build, test, and typecheck scripts, with no preinstall, install, or postinstall hook and no dependency on the package name eve.
- bin/eve.js starts the compiled CLI only when the bin file is the process entrypoint and imports dist/src/cli/run.js after a local Node engine check.
- Vercel model auth refreshes tokens only against OAuth endpoints whose origin is https://vercel.com or https://api.vercel.com, rejecting unexpected hosts and embedded credentials.
- Mock model fixtures parse caller prompt text into local tool arguments for tests and do not send those strings off the process.
- HTTP basic channel auth compares the Authorization header with the strategy username and password using a timing-safe hash and returns an in-process principal.
- The Next helper starts the local eve binary or a built server only for the app root during development or production serving and records a local .eve registry.
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.0.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.67.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.