eve@0.66.0
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 29d ago · by lpm-firewall-aiStatic inspection found no lifecycle hook or concrete malicious behavior. The required source paths show ordinary CLI, authentication, fixture, and OIDC functionality.
Decision evidence
public snapshot- Package metadata exposes a CLI and contains no install lifecycle hook.
- The CLI runs only when invoked directly and imports the compiled CLI entrypoint.
- Vercel OAuth endpoint discovery restricts endpoints to Vercel origins.
- Mock fixture code exports test-oriented helpers only.
- HTTP Basic authentication compares hashed credentials with a timing-safe comparison.
- The bundled OIDC verifier uses Vercel's JWKS endpoint.
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.66.0.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.66.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.