eve@0.76.0
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe inspected findings are tied to the package's invoked CLI and documented integration code; source inspection did not establish an active attack. The Vercel token is sent to the Vercel AI Gateway for access validation, and the GitHub integration describes repository-scoped credentials.
Decision evidence
public snapshot- package.json exposes a CLI entry point and a built distribution; it declares no install lifecycle hook.
- bin/eve.js dynamically imports the package's CLI entry point when invoked.
- Vercel auth code sends a bearer token to Vercel's AI Gateway credits endpoint as part of access validation.
- MCP skills code registers skill resource handlers; it does not establish credential collection or external transmission.
- HTTP Basic auth compares supplied credentials with configured credentials using timing-safe comparison.
- GitHub guidance describes repository-scoped credentials and routes authenticated GitHub operations through the gh tool.
Source & flagged code
9 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 · L2Package source references dynamic require/import behavior.
bin/eve.jsFindings
Affected versions and remediation
This report applies to eve@0.76.0.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.76.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.