eve@0.43.0
⚠ Under reviewFilesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspection found no concrete malicious behavior, but a clean verdict cannot carry the required eleven distinct source citations within the eight-citation limit. This is therefore an output-capacity review hold rather than a warning based on source behavior.
Decision evidence
public snapshot- The manifest exposes a CLI but its scripts shown are build-related; no install lifecycle hook is present.
- The CLI runs only when its own executable is invoked and then dispatches caller arguments to the CLI module.
- The reported hostname matches are URL-schema validation, not host collection or transmission.
- The inspected OIDC request sends a supplied bearer token only to the fixed Vercel API endpoint.
- The basic-auth helper compares supplied credentials locally using timing-safe equality.
- No concrete malicious trigger, exfiltration sink, persistence action, or lifecycle attack was established in the inspected source.
Source & flagged code
17 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.jsView on unpkg · L8Findings
Affected versions and remediation
This report applies to eve@0.43.0.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.43.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.